Jari Pennanen

# codePointAt Wording like "code point value of the UTF-16 encoded code point" seems confusing. I think MDN is clearer with saying it's *Unicode code point*. Though MDN too has...

MDN says that `codePointAt` pos is *index*, just like with `charCodeAt`. > code point starting at the specified string index Only thing where UTF16 is relevant with `codePointAt` is probably...

@fatcerberus interesting. Isn't looping over code points more succintly done with ```typescript for (let char of [...text]) { let codepoint = char.codePointAt(0); // ... } ``` (I happen to make...

That's all quiet interesting, I will study that implementation. Maybe the docs could mention at least that for all unicode points there exists a unicode character usually with a glyph....

That upstream issue is now merged? And #89 is closed. Is there other problems?

I have implemented it a long time ago with tests. Maybe I should put it online, it does however work a bit differently at times.

Hello again, here you go, I managed to dump it, I'm not sure if this is the "latest" since I use this on so many projects: https://github.com/Ciantic/jQuery.formJSON

@bchavez My https://github.com/Ciantic/jQuery.formJSON does have setter, and some rough tests. If you still need it. I'm transitioning to react where this is rarely needed anymore, it also provides type safety...

Why are they not important for functions? Memoize is just as needed in functions as well as in classes. Also for currying, who doesn't curry their functions ;) If problem...

Yes, I would like this for C#, it's really hard to figure out. I guess google.rpc.Status should be inserted in trailers, and embedding e.g. google.rpc.BadRequest inside that. But no examples...