On Friday, 23 June 2017 at 04:03:04 UTC, Adam D. Ruppe wrote:
On Friday, 23 June 2017 at 02:49:27 UTC, Mike wrote:
My approaches are right now for -betterC to be a filthy hack to
get it working quick, and I still have a bunch of ways I want
to improve the implementation and compiler interface i
I have a class Foo, which has functions a(), b(), and c().
I have a class Bar that has baz, an instance of Foo.
How do I link Bar.b() -> baz.b() without also linking Foo.a() and
Foo.c()?
I know we can do an alias this, but I only want to link over b().
Instead of passing std.range.zip a set of ranges as different
arguments, is it possible to hand the m a range of ranges, and
get them to zip together each element of every subrange?
I'm making a calendar (basically improvements to
https://wiki.dlang.org/Component_programming_with_ranges) and I'm
getting a lot of `cannot deduce function from argument types`
errors when using range-based mapping code.
Here's my current code: https://pastebin.com/TqAkggEw
My testing: `rdmd --
On Sunday, 25 February 2018 at 18:39:31 UTC, ARaspiK wrote:
I'm making a calendar (basically improvements to
https://wiki.dlang.org/Component_programming_with_ranges) and
I'm getting a lot of `cannot deduce function from argument
types` errors when using range-based mapping code.
Here's my cur
On Sunday, 25 February 2018 at 20:18:27 UTC, Paul Backus wrote:
On Sunday, 25 February 2018 at 16:22:19 UTC, ARaspiK wrote:
Instead of passing std.range.zip a set of ranges as different
arguments, is it possible to hand the m a range of ranges, and
get them to zip together each element of every
I'm creating a minimal DRuntime (for messing around). Right now,
I have a very basic program that doesn't even link to the C
runtime, and uses syscalls for everything. I'm trying to
implement alloca so that I can parse arguments (long story), and
so I went to druntime/src/rt/alloca.d.
Everyth
