7 ms·
And the typesystem is built in a way that it does not really help you due to typechecking being so slow. Make an error/begin refactoring in ocaml: just follow t
by emoII 1y ago
And the typesystem is built in a way that it does not really help you due to typechecking being so slow.
Make an error/begin refactoring in ocaml: just follow the typechecker until you’re done.
Make an error/begin refactoring in swift: you plan ahead because the typechecker will crash with a timeout or give you non-root-cause errors.
Yesterday I changed the signature of a method, and instead of complaining at the callsites I got a ”ambiguous method” error for a built in SwiftUI view modifier. Kinda hard to track down if you’re not completely aware of the changes you’ve made
- happytoexplain 1y agoThis falls under the "new frameworks" category I glossed over. SwiftUI, SwiftData, etc, are failures in my opinion. SwiftUI in particular abuses the type system. In your own code the type system is very helpful.
- cosmic_cheese 1y agoYep. If you’re writing good code that avoids common smells things are perfectly speedy. Usually if you’re making the compiler grumpy you should be sitting back and reconsidering your design anyway.
- zffr 1y agoIf you do a lot with combine publishers, then you might also have a hard time with the type system
- mpweiher 1y agoIf just about every big new framework in a language is a failure, what does that say about the language?