Kyle Simpson
Kyle Simpson
Pass in various code snippets, verify the error messages produced.
There's nothing to do for this issue... I just want to document this quirk somewhere. ```js var x; foo(x); x = 3; foo(x); function foo(a = number) {} ``` Think...
`check(..)` should return an object with the error/info messages, as well as a `transform()` method on it that will do the transformation of the runtime-assertion bits of the code.
Support basic JSON configs for disabling certain errors
Keeping notes of TODOs for TypVal. This list will be updated as progress occurs. * Embedded External Annotations: allow annotating types/signatures for external ```js "#extern foo" < int; var x...
Type exceptions: allow more fine-grained control over which errors you see. For example: ```js var x = 42; var y = "foo"; var z = [1,2,3]; if (x) { .....
* Compiler insert parameter type assertions (and remove the annotations) ```js function foo(x = int, y = bool`true`) { .. } ``` → ```js function foo(x,y = true) { x...
Define lookup mappings from typeID (like "int") to friendly type names (like "integer") for the purposes of error messages. Similar to `getTypeID(..)`. Like this: ```js getTypeName("int"); // "integer" getTypeName({ inferred:...
( I don't know why the conversation in #194 was locked (seems a silly overreaction), but whatever. I'm reopening discussion now. ) The proposed IETF RFC we had been discussing...
http://lists.openid.net/pipermail/openid-security/2010-July/001156.html I'm wondering if you guys are aware of this report and if it affects your implementations (specifically your PHP5 one)? I use your lib but I want to know...