On Monday, 16 October 2017 at 20:58:43 UTC, Martin Nowak wrote:
On Friday, 13 October 2017 at 17:08:18 UTC, Steven
Schveighoffer wrote:
I keep https://github.com/MartinNowak/bloom also as
example/scaffold repo, it's using an automated docs setup
with gh-branches.
Just create a doc deployment
On Tuesday, 24 October 2017 at 19:05:02 UTC, Martin Nowak wrote:
On Tuesday, 24 October 2017 at 14:47:02 UTC, Steven
Schveighoffer wrote:
iopipe provides "infinite" lookahead, which is central to its
purpose. The trouble with bolting that on top of ranges, as
you said, is that we have to copy
On Tuesday, 24 October 2017 at 14:47:02 UTC, Steven Schveighoffer
wrote:
iopipe provides "infinite" lookahead, which is central to its
purpose. The trouble with bolting that on top of ranges, as you
said, is that we have to copy everything out of the range,
which necessarily buffers somehow
On 10/24/17 5:32 AM, Martin Nowak wrote:
On Monday, 23 October 2017 at 16:34:19 UTC, Steven Schveighoffer wrote:
On 10/21/17 6:33 AM, Martin Nowak wrote:
On 10/19/2017 03:12 PM, Steven Schveighoffer wrote:
On 10/19/17 7:13 AM, Martin Nowak wrote:
On 10/13/2017 08:39 PM, Steven Schveighoffer
On Monday, 23 October 2017 at 16:34:19 UTC, Steven Schveighoffer
wrote:
On 10/21/17 6:33 AM, Martin Nowak wrote:
On 10/19/2017 03:12 PM, Steven Schveighoffer wrote:
On 10/19/17 7:13 AM, Martin Nowak wrote:
On 10/13/2017 08:39 PM, Steven Schveighoffer wrote:
It's solving a different problem
On 10/21/17 6:33 AM, Martin Nowak wrote:
On 10/19/2017 03:12 PM, Steven Schveighoffer wrote:
On 10/19/17 7:13 AM, Martin Nowak wrote:
On 10/13/2017 08:39 PM, Steven Schveighoffer wrote:
What would be nice is a mechanism to detect this situation, since the
above is both un-@safe and incorrect
On 10/19/2017 03:12 PM, Steven Schveighoffer wrote:
> On 10/19/17 7:13 AM, Martin Nowak wrote:
>> On 10/13/2017 08:39 PM, Steven Schveighoffer wrote:
>>> What would be nice is a mechanism to detect this situation, since the
>>> above is both un-@safe and incorrect code.
>>>
>>> Possibly you could
On 10/19/17 7:13 AM, Martin Nowak wrote:
On 10/13/2017 08:39 PM, Steven Schveighoffer wrote:
What would be nice is a mechanism to detect this situation, since the
above is both un-@safe and incorrect code.
Possibly you could instrument a window with a mechanism to check to see
if it's still
On 10/13/2017 08:39 PM, Steven Schveighoffer wrote:
> What would be nice is a mechanism to detect this situation, since the
> above is both un-@safe and incorrect code.
>
> Possibly you could instrument a window with a mechanism to check to see
> if it's still correct on every access, to be used
On Tuesday, 17 October 2017 at 12:28:28 UTC, Steven Schveighoffer
wrote:
Is the plan to put this into Phobos? If so, I would put it
under std/experimental/io. However, if not, it should not be
std/io.
I don't know yet how it will turn, but phobos is very much in
need of a better Files and
On Tuesday, 17 October 2017 at 13:45:02 UTC, Suliman wrote:
I was thinking about using Jason White's io library, but I
haven't seen him around in a while
Yes, it would be interesting if you will get some from his lib.
He have very good API
I previously collaborated a bit on that library as it
I was thinking about using Jason White's io library, but I
haven't seen him around in a while
Yes, it would be interesting if you will get some from his lib.
He have very good API
On 10/16/17 4:56 PM, Martin Nowak wrote:
On Monday, 16 October 2017 at 19:36:20 UTC, Dmitry Olshansky wrote:
Dmitry hold off on this if you were going to do it. I have been
looking at Jason White's io library, and think I'm going to just
extract all the low-level types he has there as a basic
On Friday, 13 October 2017 at 17:08:18 UTC, Steven Schveighoffer
wrote:
I keep https://github.com/MartinNowak/bloom also as
example/scaffold repo, it's using an automated docs setup with
gh-branches.
Just create a doc deployment token
(https://github.com/settings/tokens) with public_repo
On Monday, 16 October 2017 at 19:36:20 UTC, Dmitry Olshansky
wrote:
Dmitry hold off on this if you were going to do it. I have
been looking at Jason White's io library, and think I'm going
to just extract all the low-level types he has there as a
basic io library, as they are fairly complete,
On Monday, 16 October 2017 at 14:45:21 UTC, Steven Schveighoffer
wrote:
On 10/12/17 8:41 AM, Steven Schveighoffer wrote:
On 10/12/17 1:48 AM, Dmitry Olshansky wrote:
On Thursday, 12 October 2017 at 04:22:01 UTC, Steven
Schveighoffer wrote:
[...]
Might be able to help you on that using
On 10/12/17 8:41 AM, Steven Schveighoffer wrote:
On 10/12/17 1:48 AM, Dmitry Olshansky wrote:
On Thursday, 12 October 2017 at 04:22:01 UTC, Steven Schveighoffer wrote:
I added a tag for iopipe and added it to the dub registry so people
can try it out.
I didn't want to add it until I had
On 10/13/17 11:59 AM, Martin Nowak wrote:
On Thursday, 12 October 2017 at 04:22:01 UTC, Steven Schveighoffer wrote:
I added a tag for iopipe and added it to the dub registry so people
can try it out.
I didn't want to add it until I had fully documented and unittested it.
On 10/13/17 12:49 PM, Martin Nowak wrote:
On Thursday, 12 October 2017 at 18:08:11 UTC, Steven Schveighoffer wrote:
Release 0.0.2 has fixes for the ddoc that I didn't notice before,
there are no actual changes in the code.
May I recommend scod? It's just a ddox theme.
On Thursday, 12 October 2017 at 18:08:11 UTC, Steven
Schveighoffer wrote:
Release 0.0.2 has fixes for the ddoc that I didn't notice
before, there are no actual changes in the code.
May I recommend scod? It's just a ddox theme.
https://github.com/MartinNowak/scod
I keep
On Thursday, 12 October 2017 at 04:22:01 UTC, Steven
Schveighoffer wrote:
I added a tag for iopipe and added it to the dub registry so
people can try it out.
I didn't want to add it until I had fully documented and
unittested it.
http://code.dlang.org/packages/iopipe
On 10/12/17 3:05 AM, Jacob Carlborg wrote:
On 2017-10-12 06:22, Steven Schveighoffer wrote:
I also want to add generated documentation. Does anyone know of a good
way to generate the ddoc (or ddox or whatever) and put it directly
into the repository for github to serve? Would be an awesome
On 10/12/17 1:48 AM, Dmitry Olshansky wrote:
On Thursday, 12 October 2017 at 04:22:01 UTC, Steven Schveighoffer wrote:
I added a tag for iopipe and added it to the dub registry so people
can try it out.
I didn't want to add it until I had fully documented and unittested it.
On 2017-10-12 06:22, Steven Schveighoffer wrote:
I also want to add generated documentation. Does anyone know of a good
way to generate the ddoc (or ddox or whatever) and put it directly into
the repository for github to serve? Would be an awesome tip for people
making projects for
On Thursday, 12 October 2017 at 04:22:01 UTC, Steven
Schveighoffer wrote:
I added a tag for iopipe and added it to the dub registry so
people can try it out.
I didn't want to add it until I had fully documented and
unittested it.
http://code.dlang.org/packages/iopipe
I added a tag for iopipe and added it to the dub registry so people can
try it out.
I didn't want to add it until I had fully documented and unittested it.
http://code.dlang.org/packages/iopipe
https://github.com/schveiguy/iopipe
If you plan on using it, expect some API changes in the near
26 matches
Mail list logo
