3 ms·
Well, you're lucky. Every so often SBT loses its mind and starts throwing spurious errors. Or, runs out of memory. Solution: restart SBT, wait for a minute for
by allengeorge 11y ago
Well, you're lucky. Every so often SBT loses its mind and starts throwing spurious errors. Or, runs out of memory.
Solution: restart SBT, wait for a minute for it to recompile the project definition; rebuild
project. That inconvenience wears on you.
- merb 11y agoActually the spurious errors didn't happen to me, however I actually use sbt tasks in intellij and deactivated every compile-server or whatever. The only thing which happens really really often is that when I coded some hours that the errors can't be displayed inside a web view and sbt loops the error, however thats not a big deal since after fixing it it goes back to normal. However my Scala project actually doesn't use too many "special" feature's I would say I actually don't use any obscure language feature, the only operator which I've written yet is a "~~" for a StringBuilder and else I actually wrote out EVERY type parameter to my function, etc. I would say we write our code so that it's readable inside all major ide's and is understandable by junior developers.