Joshua Shinavier
Joshua Shinavier
Another approach to this problem is simply to follow Algorithm W in storing type annotations in two places: domain types for lambdas, and forall types for 'let' bindings. It is...
Keeping this issue open only as long as it takes to adjust the Java coder to the new inference implementation. The new format for inferred type annotations has been finalized,...
This issue is not useful any longer. While the Java coder has not caught up yet, the Python coder uses only System F -style type annotations. The Java coder will...
Note: even JSON serialization currently requires an external library. In order to serialize JSON ourselves, #172 will need to be completed first. Consider the imports in the current JSON serde...
Note: the reason `equal` and `compare` usually work well in Haskell is that we usually generate `deriving (Eq, Ord)` in the type definitions. That is to say, we are essentially...
I am sure. It is just a question of when to do it. 32-bit integer arithmetic is the only kind which is currently used by the kernel or coders, so...
Note: the only tricky thing about this change is in the Haskell coder, where we need to represent `ByteStrings` in some way (e.g. as a list of hex integers like...
Note: these validation modules can be organized into the new kernel namespacing scheme as `hydra.validate.core`, `hydra.validate.module`, etc. General-purpose helpers can go in `hydra.validation`.
Yes, go ahead and add me. Btw. you can exclude Hydra-Scala for now. It is still there, but it is very stale and probably will not be updated until after...