Rafael Schouten

hah sorry I should have broken that up

5 This was to make it clear that traits and tests are not the same thing, and probably need to stay decoupled. So its really in opposition to 4. I...

7. This was simply saying that interfaces are not just about defining methods, and point 1 is incomplete. You can define all the methods in the AbstractArray interface of your...

yeah, 5 :sweat_smile:

Thanks these are interesting ideas! Here I'm making types construct mock objects for testing, to get around `_return_type` like problems, but it does feel a bit clunky. Your idea is...

More like some interface checks might be too expensive to use compile-time checks and would need to work like they do currently in this package, with traits being separated from...

> One could also say, that one would expect the cost of both defining an interface and stating that an interface is implemented should be purely compile time and not...

Yeah I can see how it looks like that! But that runs in the tests (originally in precompile), not actually when you check a trait. The idea of putting it...

But does it make sense now that `x -> age(x) >= 0` does not actually run at runtime? One of the main questions with designing this thing is how to...

> Do you mean you want to check instances of structs at compile time by creating and testing them inside the macro expansion step? So it's still value based, just...