Am 10.10.2013 03:25, schrieb Martin Nowak:
On 10/06/2013 10:18 AM, Sönke Ludwig wrote:
I also see no fundamental reason why the API forbids
extension for shared sting tables or table-less lexing.

The current API requires to copy slices of the const(ubyte)[] input to
string values in every token. This can't be done efficiently without a
string table. But a string table is unnecessary for many use-cases,
so the API has a built-in performance/memory issue.

But it could be extended later to accept immutable input as a special case, thus removing that requirement, if I'm not overlooking something. In that case it still is a pure implementation detail.

Reply via email to