3 ms·
> The language was released in 2014. The error messages are being actively worked on. They were vastly improved with 2.0. Well, "Segmentation Fault" hasn't rea
by cballard 11y ago
> The language was released in 2014. The error messages are being actively worked on. They were vastly improved with 2.0.
Well, "Segmentation Fault" hasn't really improved, and it's reasonably common when type inference in closures breaks down.
- autoreleasepool 11y agoI'm unfamiliar with this situation. Is this truly a common problem? I'd love to see a source code example to test.
- cballard 11y agoPretty consistent for me in projects that are: - Sufficiently large - Contain a closure that contains a compiler error - Which the compiler tries to work around via type inference, causing another error