Michel Hermier

About your initial concern, it should be factorized to a utility function method in the first place. In the future, you may wan't to return an hypothetical `TypeError` or whatever....

This is the reason I said you should abstract the behavior in a function, like in the assert library. Duplicating even a one liner is a bad idea... Don't give...

I don't have right now, but it is a simple node transform. So it is only a matter adding the tokens, matching them into a node and performing the transform...

OT @PureFox48 out of curiosity do you have command line argument parser ? I have one that is not really OO and quite a lot manual (though I can factorize...

Too simple but confirms that what I do is *right*, it is only a matter of making it more OO then ;)

Could someone with more knowledge than me verify licencing of it. The python licence seems troublesome too add to the project.

The real question is will that contaminate the MIT Licencing of the project ?

I will probably hate myself later for proposing that, but maybe we should implement it ourself, by augmenting our own functions. That way we could do token scanning and parsing...

Maybe we can conditionally support `strtod_l`. It seems supported on a a fair amount of systems now with some kind of limitations on some like `#define _GNU_SOURCE` on glibc. Dunno...

> > We can't produce a proper binding. > > I'm not sure what this means, could you please clarity? The major issue is that `uv_req_t` does not reference the...