4 ms·
That would go under bug fixes. But you could help us by filing tickets on trak. The general issue (type volatility) is well known, but you have discovered a lo
by modersky 16y ago
That would go under bug fixes. But you could help us by filing tickets on trak. The general issue (type volatility) is well known, but you have discovered a loophole which wasn't.
- deleted 16y ago[deleted]
- scala_hacker 16y agoThe bug has already been listed in trac for quite some time now -- that is how I found out about it. However, it is unclear how you can expect to detect conflicting member infos and still retain separate compilation. Still, I look forward to you proving me wrong.