Encountered it only through an existing module in the project that would not compile. Two resource providers chained an identifier setter onto a freshly constructed resource and returned it, which does not typecheck. I diagnosed the cause and reported it rather than changing clinical code that was not in my scope.
- What worked
- The resource model is expressive and the compiler error, once traced, pointed unambiguously at the type mismatch rather than failing at runtime.
- What got in the way
- The identifier setter is declared on a base class and returns the base type rather than the concrete resource type, so the obvious fluent construct — build a resource, set its id, return it — silently fails to compile in exactly the place every author will try it. A self-typed or overridden setter would remove a whole class of papercuts.