Package maintainers and Hackage trustees are allowed to edit certain bits
of package metadata after a release, without uploading a new tarball.
Note that the tarball itself is never changed, just the metadata that is
stored separately. For more information about metadata revisions, please
refer to the
Hackage Metadata Revisions FAQ.
No. |
Time |
User |
SHA256 |
-r1 (infernu-0.0.0.0-r1) |
2015-04-15T19:53:38Z |
NoamLewis |
9031a563d3308144acf60b4ee57dc0c45bdf2dca486a56664e005d92efd815b1
|
|
Changed description
from This version is highly experimental and may set your computer on fire (also, a lot of JS is not supported yet, so it may not be very useful.)
Infernu is a type checker for JavaScript. Since JavaScript is dynamically and weakly typed, it makes no sense to talk about "type errors" in arbitrary JavaScript code.
Consequently Infernu makes assumptions about the code and expects it to follow certain rules that
are not required by plain JavaScript (for example, implicit coercions such as `3 + 'a'` are not
allowed.)
Infernu's type system is designed for writing dynamic-looking code in a safe statically type-checked
environment. Type annotations are not required (though they would be nice to support, for various
reasons). Instead, Infernu *infers* the types of expressions by examining the code. If the inferred
types contradict each other, Infernu reports the contradiction as an error.
Infernu places restrictions on JS programs that are otherwise valid. In other words, Infernu is a
**subset of JavaScript**. Infernu tries to strike a balance between type system complexity and
dynamic-style coding flexibility.
See the .md files included in the package for more information.
to This version is highly experimental and may set your computer on fire (also, a lot of JS is not supported yet, so it may not be very useful.)
Also, the latest version is always at <https://github.com/sinelaw/infernu>. The version here (on hackage) is most certainly outdated.
Infernu is a type checker for JavaScript. Since JavaScript is dynamically and weakly typed, it makes no sense to talk about "type errors" in arbitrary JavaScript code.
Consequently Infernu makes assumptions about the code and expects it to follow certain rules that
are not required by plain JavaScript (for example, implicit coercions such as `3 + 'a'` are not
allowed.)
Infernu's type system is designed for writing dynamic-looking code in a safe statically type-checked
environment. Type annotations are not required (though they would be nice to support, for various
reasons). Instead, Infernu *infers* the types of expressions by examining the code. If the inferred
types contradict each other, Infernu reports the contradiction as an error.
Infernu places restrictions on JS programs that are otherwise valid. In other words, Infernu is a
**subset of JavaScript**. Infernu tries to strike a balance between type system complexity and
dynamic-style coding flexibility.
See the .md files included in the package for more information.
|
-r0 (infernu-0.0.0.0-r0) |
2015-04-15T15:37:48Z |
NoamLewis |
6413fb08059ca68f5ed1a6d4812464200cf086f379104e753e256ef60ba343dd
|
|
|