vyzo

Results 640 comments of vyzo

Also check the compiler default flags, maybe use lates gnu standard flags?

if you want to help out, you can definitely share it with @drewc. DM me on gitter or email me at vyzo at hackzen.org to discuss details.

It does not mark exports in any way, and honestly this should not be a runtime check at all! I think the right way yo do it is to have...

this is done now, all symbols from gambit.sld are part of the runtime exports.

Moving to the backlog, as the multipackage repo thing doesn't have such a high impact.

A better syntax proposal that doesn't use keywords: - `:=` for checked contracts - `:-` for type assertions - `:>` for return types So here is a definition for a...

We can also extend struct and class definitions to add type annotations to members: ``` (defstruct X ((a :- fixnum?) ...) ...) (defclass X ((a :- fixnum?) ...) ...) ```

Yes, the prefix syntax will be raw annotation: `(begin-annotation (type ...) expr)`. The `:std/contract` macros will expand to that.

ok, fair enough, we can us `::` for return type.