What library functionality would you most like to see in D?

[Roman D. Boiko]

On Friday, 11 May 2012 at 08:37:06 UTC, Jacob Carlborg wrote:
> A couple of questions:
>
> * What's the sate of the lexer
I consider it a draft state, because it has got several rewrites 
recently and I plan to do more, especially based on community 
feedback. However, implementation handles almost all possible 
cases. Because of rewrites it is most likely broken at this 
moment, I'm going to fix it ASAP (in a day or two).

Lexer will provide a random-access range of tokens (this is not 
done yet).

Each token contains:
* start index (position in the original encoding, 0 corresponds 
to the first code unit after BOM),
* token value encoded as UTF-8 string,
* token kind (e.g., token.kind = TokenKind.Float),
* possibly enum with annotations (e.g., token.annotations = 
FloatAnnotation.Hex | FloatAnnotation.Real)

> * Does it convert numerical literals and similar to their 
> actual values
It is planned to add a post-processor for that as part of parser, 
please see README.md for some more details.

> * Does it retain full source information
Yes, this is a design choice to preserve all information. Source 
code is converted to UTF-8 and stored as token.value, even 
whitespaces. Information about code unit indices in the original 
encoding is preserved, too.

> * Is there an example we can look at to see how the API is used
TBD soon (see Roadmap in the readme file)

> * Does it have a range based interface
Yes, this is what I consider one of its strengths.