On Wednesday, 1 May 2019 at 12:29:18 UTC, Rudy Raab wrote:
On Tuesday, 30 April 2019 at 20:35:11 UTC, Bastiaan Veelo wrote:
On Tuesday, 30 April 2019 at 13:59:52 UTC, Rudy Raab wrote:
The error was on line 36, which is the format, not my bad
slice. Is there a reason for this, or is it a bug
T
On Tuesday, 30 April 2019 at 20:35:11 UTC, Bastiaan Veelo wrote:
On Tuesday, 30 April 2019 at 13:59:52 UTC, Rudy Raab wrote:
The error was on line 36, which is the format, not my bad
slice. Is there a reason for this, or is it a bug
The message is correct when not using dub:
https://run.dlang.
I didn't want to immediately declare this a compiler/runtime bug
without making sure I wasn't crazy/misinterpreting things.
Backstory is this: I was writing a library for dealing with some
special corporate data to (de)serialize to/from a binary format
and tweaking things to get the output to
On Sunday, 24 June 2018 at 21:28:06 UTC, aliak wrote:
On Sunday, 24 June 2018 at 20:33:32 UTC, Rudy Raab wrote:
So I have an XLSX (MS Excel 2007+ file format) library that I
wrote (https://github.com/TransientResponse/dlang-xlsx) that
I recently converted from std.xml to dxml. That went well a
So I have an XLSX (MS Excel 2007+ file format) library that I
wrote (https://github.com/TransientResponse/dlang-xlsx) that I
recently converted from std.xml to dxml. That went well and it
still works (much faster too).
Now I had the idea that a lazy forward range API (like dxml
itself or std
