Yang Guo

General goal makes sense to me. But I'm uncertain how standardization would work, considering that Error.stack nor console outputis standardized.

Hi, I'm part of the V8 team. I'm surprised that this is somehow a new situation. V8 does not use semantic versioning (and never has), so distributing V8 as shared...

I see. Thanks for the context. Node.js maintains a gyp build, and may introduce a cmake build, which includes build configs for V8. Would that be a solution to this...

Let me clarify: V8 has *never* been intended to be distributed as shared library. This is a direct result of V8 not adopting semantic versioning. The only reason V8 supports...

As @littledan mentioned, this is an experimental feature in V8. The comment in the regexp parser describes the current syntax we are using: ``` // Parse the property class as...

We considered doing loose matching and having a "In"-prefix for blocks. But having thought about it, we decided against either. Looking at Perl, it seems to be a good idea...

I thought the underscore is actually part of the name. That's what PropertyAlias.txt and PropertyNameAlias.txt as well as ICU suggest.

Thanks for following up on this, Mathias! Having followed the unicode mail thread, I think I can get behind the idea of considering whitespace, hyphens and underscores as equivalent, when...

If matching `Blocks.txt` is not really that important, I'm actually hesitant to follow UAX44-LM2 at all, including whitespace and underscore. If we simply follow UAX44-LM2, we end up with loose...

@srl295 I don't think exposing a way to test for property value for a particular character should affect this proposal.