ctfe bug?

Johannes Pfau spam at example.com
Wed Dec 21 23:57:36 PST 2011

Johannes Pfau wrote:
> Has this bug already been filed? I could possibly circumvent it by making
> ragel use array indexing instead of pointers, but that'd be a performance
> issue for runtime code as well.

OK, I found a workaround:
If I use

data[x] = parse!ubyte(input[p-input.ptr-2 .. p-input.ptr], 16);

instead, it works. So the issue is related to pointer slicing in ctfe.

More information about the Digitalmars-d-learn mailing list