On Tuesday, September 13, 2011 14:04 Dmitry Olshansky wrote: > Speaking of source there are few artifacts that should end up in std.uni > and not in std.regex: > CodepointSet and CodepointTrie, and unicode property tables. > I'd rather have them all accessible to user, but their interface is > admittedly clunky, I'm open to ideas on better API.
I suspect that there's value in reviewing the unicode stuff separately, and if it affects std.regex' API at all (as opposed to being simply an implementation detail), I'd suggest that we review and sort out the unicode stuff before we review then new std.regex, since that would then have definite impact on std.regex, and it affects a lot more than just std.regex. If the unicode stuff is entirely an implementation detail of std.regex and is not in the API, then we can review the unicode stuff separately and make std.regex use the stuff in std.uni once it's in there, but if you're doing major unicode stuff, I think that that's significant enough to merit its own review. - Jonathan M Davis
