Rob Loach

This isn't replacing premake/make with cmake, nor would I want to do that. This is just adding the CMake definition file so you can use cmake to both build and...

Thanks! Took on a few things... - Moved to wren code to make use of the utf8 functional codepoints - Renamed to `.lowerCase` to look more the other wren style...

> Unfortunately, migrating ASCII to Unicode in this case is a breaking change. While I can understand how you could interpret that as a breaking change, I would propose that...

Technically true, but how many people would use `.lower` and hope that it doesn't lowercase UTF-8? :upside_down_face: .... We're [edge-casing](https://en.wikipedia.org/wiki/Edge_case) at this point.

Found a potential list for UTF-8 characters https://pastebin.com/fuw4Uizk

That's a reasonable compromise. https://cs.stanford.edu/people/miles/iso8859.html

> - Don't support Unicode upcase/downcase in Core, it's a user/library concern > - Realizing this is a general problem where it would be useful to extend core classes -...

Could you take advantage of `vm->config.userData` here?

[Asset Packagist](https://asset-packagist.org/) could be a solution to avoid introducing another package manager. You add the Composer repository, and then have access to the npm repos... ``` "require": { "npm-asset/jquery": "^2.2"...

Thanks for the investigation! Looks like PECL/Pickle may be the way to go, if effort picks up again. Easiest may be repositories of asking to build the packages by self.