On Thursday, 8 March 2018 at 22:53:11 UTC, aberba wrote:
On Thursday, 8 March 2018 at 09:35:08 UTC, Andrew Benton wrote:
On Thursday, 8 March 2018 at 07:54:29 UTC, Jacob Carlborg
wrote:
On Thursday, 8 March 2018 at 07:20:53 UTC, Radu wrote:
This guys says that vide.d works
https://forum.dlang
On Wednesday, 7 March 2018 at 14:54:22 UTC, aberba wrote:
I notice from the Dockerfile you build and copy the binary to
alpine directly. Why don't you build and serve from alpine
directly?
This way the final images won't contain the build environment,
thus they are really small: 9 and 12 MB o
I packaged a hello world vibe.d http server into a docker image.
It's only 12 MB, and boots up real fast. I can run this on my ARM
based NAS, pretty sweet.
docker run -it --publish : tam4s/hello-vibe-x86_64
or
docker run -it --publish : tam4s/hello-vibe-armv7l
source
On Wednesday, 7 March 2018 at 04:28:11 UTC, Seb wrote:
For run.dlang.io, I fetch all dependencies and build them into
the Docker image. That has the advantage that executions with
dub packages are a lot faster.
It's just dub fetch and dub build though. Take a look:
https://github.com/dlang-tou
I have a Dockerfile to build a vibe.d project. Docker has a nice
caching system so it continues building the docker image from the
step where it's needed when something changes. This is typically
at the step of adding my source files, then building the binary.
The problem is that fetching and
On Wednesday, 27 April 2016 at 16:09:42 UTC, Tamas wrote:
Have you received registration confirmation after registering
via PayPal? I'm asking because the payment links are on an
unsecured page, and the credit card transaction was first
refused because of potential fraud, so I had to make a cal
Have you received registration confirmation after registering via
PayPal? I'm asking because the payment links are on an unsecured
page, and the credit card transaction was first refused because
of potential fraud, so I had to make a call to make it happen.
I think the problem can be separated into two:
1. Guarantee a given Big O complexity of a function, (that's what
matters for most cases),
2. Guarantee / tell the worst case execution time / CPU cycles of
a given @constanttime function.
Combining these two, we can calculate the worst case execiti
On Wednesday, 23 March 2016 at 17:29:55 UTC, Nick Treleaven wrote:
On Monday, 21 March 2016 at 23:09:27 UTC, Tamas wrote:
On Monday, 21 March 2016 at 11:48:52 UTC, Seb wrote:
Could you try to point out whats wrong with map & filter?
It's hard to do stuff like this:
assert(9.iota.emit!(int,(pu
On Monday, 21 March 2016 at 11:48:52 UTC, Seb wrote:
Could you try to point out whats wrong with map & filter?
It's hard to do stuff like this:
assert(9.iota.emit!(int,(put,a){if(a%2) put(a*a); if(a%3==0)
put(a);}).equal([1,9,3,25,6,49]));
I just run into this. Would be nice to have this! There's no
reason why chunks should only work on ForwardRanges.
11 matches
Mail list logo