On Wednesday, 15 August 2018 at 09:31:48 UTC, Russel Winder wrote:
That's the battle isn't it. Should the system that builds be
the system that also manages the packages for the build (cf.
Dub, Cargo, Go, Mason), or should the two be kept separate (cf.
CMake, Meson, SCons, Make).
The debate
On Thursday, 16 August 2018 at 12:25:14 UTC, aliak wrote:
Hi
See: https://optional.dub.pm
I've totally revamped the Optional type and am now quite happy
with. It has a range interface and safe dispatching and can be
used to 1) avoid null dereferencing, 2) have non-null
guarantees, and 3)
On Thursday, 16 August 2018 at 12:25:14 UTC, aliak wrote:
It's also @nogc and @safe
No it's not. Not dispatching at least. Dunno why though. Seems
safey is because taking an address. Nogc will have to look in to.
On Thursday, 16 August 2018 at 15:38:50 UTC, Paul Backus wrote:
On Thursday, 16 August 2018 at 12:25:14 UTC, aliak wrote:
Hi
See: https://optional.dub.pm
Looks great!
auto john = some(new Person());
Would it also work to leave off the `some` here and skip the
first `dispatch` in the
On Thursday, 16 August 2018 at 12:25:14 UTC, aliak wrote:
Hi
See: https://optional.dub.pm
Looks great!
auto john = some(new Person());
Would it also work to leave off the `some` here and skip the
first `dispatch` in the following lines? (i.e., make `john` a
`Person` rather than an
Hello,
I just released v0.9.0 of dlang-requests. This is large
performance improvement and code refactoring release. Nothing
changed in API and everything should work as before (hopefully
better and faster)
What's new:
1. Connection pool for each HTTPRequest structure added. This
give
Hi
See: https://optional.dub.pm
I've totally revamped the Optional type and am now quite happy
with. It has a range interface and safe dispatching and can be
used to 1) avoid null dereferencing, 2) have non-null guarantees,
and 3) show clear intent where there may or may not be a value.
