On Tuesday, 19 June 2018 at 13:04:24 UTC, Steven Schveighoffer
wrote:
On 6/19/18 7:18 AM, Jacob Carlborg wrote:
On 2018-06-11 16:45, Steven Schveighoffer wrote:
I just pushed v0.1.1 -- I realized that I never *actually*
compiled on
windows, and there were a couple things that didn't work.
On 2018-06-19 15:04, Steven Schveighoffer wrote:
I just set up travis to do the Linux/mac testing. I need to add appveyor
as well, but haven't gotten to it. I'm a complete CI noob, so I'm
learning slowly :)
To save you some trouble, AppVeyor supports both a YAML, like Travis,
and a web UI to
On 6/19/18 7:18 AM, Jacob Carlborg wrote:
On 2018-06-11 16:45, Steven Schveighoffer wrote:
I just pushed v0.1.1 -- I realized that I never *actually* compiled on
windows, and there were a couple things that didn't work.
Note: the examples still don't work as they rely on openDev, which is
On 2018-06-11 16:45, Steven Schveighoffer wrote:
I just pushed v0.1.1 -- I realized that I never *actually* compiled on
windows, and there were a couple things that didn't work.
Note: the examples still don't work as they rely on openDev, which is
only available on Posix systems now.
I need
On Sunday, 17 June 2018 at 04:52:07 UTC, Martin Nowak wrote:
On 06/10/2018 10:10 PM, Steven Schveighoffer wrote:
Note that the new io library also supports sockets, which
IODev did not have support for, AND has a pluggable driver
system, so you could potentially use fiber-based async io
On 06/10/2018 10:10 PM, Steven Schveighoffer wrote:
> Note that the new io library also supports sockets, which IODev did not
> have support for, AND has a pluggable driver system, so you could
> potentially use fiber-based async io without rebuilding. It just makes a
> lot of sense for D to have
On 6/13/18 12:03 PM, Steven Schveighoffer wrote:
I'm going to push this (I'll do some tests for the other widths to make
sure it works for all UTF), but if you have any more things you want to
work at CTFE, submit some issues on the github project.
v0.1.2 released
-Steve
On 6/13/18 8:35 AM, bauss wrote:
Does iopipe work with CTFE?
It may work in some cases. Some of the things it does are not conducive
to CTFE working well -- like using a buffer. But generally at compile
time, you don't want to use a buffer.
But I would expect, for instance, using
On Sunday, 10 June 2018 at 20:10:31 UTC, Steven Schveighoffer
wrote:
-Steve
Does iopipe work with CTFE?
On Tuesday, 12 June 2018 at 14:00:32 UTC, Steven Schveighoffer
wrote:
File.byLine is fast, but only because of the underlying
non-range tricks it uses to achieve performance. And iopipe
still is 2x faster.
I wish iopipe was around a little bit earlier so I could use it
in my small project.
On Tuesday, 12 June 2018 at 13:51:56 UTC, Steven Schveighoffer
wrote:
On 6/12/18 1:51 AM, DigitalDesigns wrote:
Could you explain some benefits specific to this
implementation and a bit of the functional aspects for a
proper overview of it's capabilities and why I should chose
this method
On 6/12/18 10:19 AM, Jesse Phillips wrote:
I plan to eventually finish the JSON parser for a releasable state,
and eventually tackle XML and a few other things.
You should definitely tackle xml by branching dxml. I'm really liking
the api.
Of course that is my plan! I would never want to
I plan to eventually finish the JSON parser for a releasable
state, and eventually tackle XML and a few other things.
-Steve
You should definitely tackle xml by branching dxml. I'm really
liking the api.
On 6/12/18 3:08 AM, Anton Fediushin wrote:
On Sunday, 10 June 2018 at 20:10:31 UTC, Steven Schveighoffer wrote:
iopipe version 0.1.0 has been released.
iopipe is a high-performance pipe processing system that makes it easy
to string together pipelines to process data with as little buffer
On 6/12/18 1:51 AM, DigitalDesigns wrote:
Could you explain some benefits specific to this implementation and a
bit of the functional aspects for a proper overview of it's capabilities
and why I should chose this method over others?
The things that I think make this approach better are:
1.
On Sunday, 10 June 2018 at 20:10:31 UTC, Steven Schveighoffer
wrote:
iopipe version 0.1.0 has been released.
iopipe is a high-performance pipe processing system that makes
it easy to string together pipelines to process data with as
little buffer copying as possible.
I saw iopipe a while
On Sunday, 10 June 2018 at 20:10:31 UTC, Steven Schveighoffer
wrote:
iopipe version 0.1.0 has been released.
iopipe is a high-performance pipe processing system that makes
it easy to string together pipelines to process data with as
little buffer copying as possible.
Nothing has really been
On 6/10/18 4:10 PM, Steven Schveighoffer wrote:
Nothing has really been changed, but it now has Windows i/o support. I
will note at this time, however, that ring buffers are not yet supported
on Windows.
I just pushed v0.1.1 -- I realized that I never *actually* compiled on
windows, and
On 6/11/18 6:14 AM, Dejan Lekic wrote:
On Sunday, 10 June 2018 at 20:10:31 UTC, Steven Schveighoffer wrote:
iopipe version 0.1.0 has been released.
iopipe is a high-performance pipe processing system that makes it easy
to string together pipelines to process data with as little buffer
On Sunday, 10 June 2018 at 20:10:31 UTC, Steven Schveighoffer
wrote:
iopipe version 0.1.0 has been released.
iopipe is a high-performance pipe processing system that makes
it easy to string together pipelines to process data with as
little buffer copying as possible.
All I can say (again,
iopipe version 0.1.0 has been released.
iopipe is a high-performance pipe processing system that makes it easy
to string together pipelines to process data with as little buffer
copying as possible.
Nothing has really been changed, but it now has Windows i/o support. I
will note at this
21 matches
Mail list logo
