Re: Extensible destructuring proposal

2015-08-04 Thread Andreas Rossberg
On 31 July 2015 at 20:09, Samuel Hapák samuel.ha...@vacuumapps.com wrote: So, do you still have objections against this proposal? Could we summarize them? @Andreas, do you still think that there is category error involved? If you want to overload existing object pattern syntax, then yes,

Re: Please help with writing spec for async JSON APIs

2015-08-04 Thread Mark Miller
+1 for line delimited JSON. It would be good to switch all users of json-seq over to it and to deprecate json-seq. Perhaps an RFC would help. On Mon, Aug 3, 2015 at 11:53 PM, Bruno Jouhier bjouh...@gmail.com wrote: RFC 7464 has a different format (0x1E at beginning of every record) and a

Re: Please help with writing spec for async JSON APIs

2015-08-04 Thread Bruno Jouhier
RFC 7464 has a different format (0x1E at beginning of every record) and a different media type (application/json-seq vs application/x-ldjson) than line delimited JSON (https://en.wikipedia.org/wiki/Line_Delimited_JSON). The 0x1E at the beginning of every record makes it hard to edit these files.

Re: Cancelable promises proposal

2015-08-04 Thread Glen Huang
Are there some example use-cases where being able to `.ignore` is preferable to having the promise reject? The purpose of .ignore() is to let promises show disinterest, by disinterest, i mean the situation that whatever happens to that promise, it shouldn't be observable to the callbacks.

Re: Cancelable promises proposal

2015-08-04 Thread Logan Smyth
Glen, sorry if this has been covered in other discussions, but it's not clear to me so I wanted to ask. Are there some example use-cases where being able to `.ignore` is preferable to having the promise reject? Promise chains are about defining flows of data and I can't really see a case where

Re: Cancelable promises proposal

2015-08-04 Thread Glen Huang
On Aug 4, 2015, at 1:32 PM, Andrea Giammarchi andrea.giammar...@gmail.com wrote: only promises that has passed through their initialization the callback would be cancelable,and this could be reflected through a `.cancelable` property That's precisely the problem. When you made a mistake

Re: Please help with writing spec for async JSON APIs

2015-08-04 Thread Bruno Jouhier
JSON is not that hard to parse incrementally. The i-json parser is implemented in C++ with a fallback JS implementation. The C++ implementation is less than 1000 locs and the JS implementation less than 400 locs. The C++ implementation is 1.65 times slower than JSON.parse but, unlike JSON.parse,

Re: Please help with writing spec for async JSON APIs

2015-08-04 Thread Dean Landolt
On Tue, Aug 4, 2015 at 9:53 AM, Mark Miller erig...@gmail.com wrote: +1 for line delimited JSON. It would be good to switch all users of json-seq over to it and to deprecate json-seq. Perhaps an RFC would help. On Mon, Aug 3, 2015 at 11:53 PM, Bruno Jouhier bjouh...@gmail.com wrote: RFC