Closed laughedelic closed 8 years ago
The problem is the same as in Loquat itself: when defining an object inside of a trait, the fqn of this trait's instance will be messed up. In loquat it's solved like this. I'm going to do something similar here.
Yes I remember this. Maybe we should mention that somewhere, but where? loquat docs/readme?
Well, it doesn't affect loquat usage anyhow. I would put it somewhere like ohnosequences/scala-guide, but it's long abandoned..
Rearrangement of the loquat/statika related things in #112 broke something in the way
manager
compat gets its fully-qualified name. I'm working on a fix.