Denis Koroskin Wrote:
> On Sat, 26 Sep 2009 22:30:58 +0400, Walter Bright
> wrote:
>
> > language_fan wrote:
> >> This starts to sound like traits (http://www.codecommit.com/blog/scala/
> >> scala-for-java-refugees-part-5). On this road D is becoming a great
> >> tribute to Scala.
> >
> > D
Walter Bright Wrote:
> bearophile wrote:
> > Walter Bright:
> >
> >> Executive summary: pure functions and immutable data structures help
> >> manage program complexity.
> >
> > At the moment in D there aren't many immutable data structures available,
> > but of course they can be written.
> >
Daniel Keep Wrote:
>
>
> Jason House wrote:
> > Dynamic casts are pure. They don't use global state, and have the same
> > output for the same reference as input. Interestingly, dynamic cast results
> > are independent of intervening mutable calls... So there
Dynamic casts are pure. They don't use global state, and have the same output
for the same reference as input. Interestingly, dynamic cast results are
independent of intervening mutable calls... So there's even greater opportunity
for optimization.
bearophile Wrote:
> I don't know much about t
Graham St Jack Wrote:
> So, what is the design of shared supposed to be then? Its time for Walter
> to buy in and tell us where this is all going - I for one am very
> confused right now.
Here's what I know:
Bartosz's ownership scheme is delayed until at least D3
Shared code will be sequent
Don Wrote:
>
> I've provided very simple solutions for both of these. I'm getting
> pretty irritated that people are acting as though these are difficult
> problems and trying to come up with convoluted solutions. Impose minimal
> semantics and it becomes trivial.
FWIW, I've liked your proposa
Robert Jacques Wrote:
> On Sun, 13 Sep 2009 18:08:57 -0400, Jeremie Pelletier
> wrote:
> .
>
> Bartosz took the concept one step further: when declared as shared, all
> methods are implicitly wrapped in synchronize blocks. He then added a
> keyword for more manual, lock-free style programm
Jeremie Pelletier Wrote:
> Jason House Wrote:
>
> > I'm glad to see I'm not the only one trying to use shared. I tried to use
> > it with 2.031 and rapidly hit bug after bug... I submitted several bug
> > reports for basic functionality, and none of it appear
I'm glad to see I'm not the only one trying to use shared. I tried to use it
with 2.031 and rapidly hit bug after bug... I submitted several bug reports for
basic functionality, and none of it appeared in the changelog.
http://d.puremagic.com/issues/show_bug.cgi?id=3089
http://d.puremagic.com/is
Don Wrote:
> Interestingly since DMD has extern(C++), it ought to be possible to
> convert a single module to D, and still link it in...
extern(C++) support in D is nearly a joke. There are some big areas for
improvement, such as support for non-virtual functions, or allowing use of new,
... I
Don Wrote:
> I've been focussing more on ICE bugs and CTFE, which have been
> annoying me more.
The focus on CTFE is pretty obvious from Walter's recent update to the
changelog.
Jeremie Pelletier Wrote:
> Jason House Wrote:
>
> > Paul D. Anderson Wrote:
> >
> > > I'm going to add Linux to my PC to get a dual-boot configuration. (I'm
> > > tired of slw start ups and want to tap into the great tools
> > > avai
Paul D. Anderson Wrote:
> I'm going to add Linux to my PC to get a dual-boot configuration. (I'm tired
> of slw start ups and want to tap into the great tools available.) The
> tutorial I'm looking at suggests Ubuntu. Is there a significant difference in
> Linux implementations? Is Ubuntu o
Jeremie Pelletier Wrote:
> Paul D. Anderson Wrote:
>
> > It's awfully quiet on the newsgroup today. Does that mean Walter is busy
> > getting the new release ready?
> >
> > Or does it only mean I'm not getting new posts :(
> >
> > Suspiciously,
> >
> > Paul
>
> It IS awfully quiet this week
Jeremie Pelletier Wrote:
> Paul D. Anderson Wrote:
>
> > It's awfully quiet on the newsgroup today. Does that mean Walter is busy
> > getting the new release ready?
> >
> > Or does it only mean I'm not getting new posts :(
> >
> > Suspiciously,
> >
> > Paul
>
> It IS awfully quiet this week
FWIW, I usually use static if instead of specialization. In D2, you can also
use if expressions as part of the template declaration. As far as your code
below, I think the declaration of M without using it is suspect. I don't have a
compiler to play with right now...
div0 Wrote:
> -BEGIN P
Ary Borenszweig Wrote:
> Jarrett Billingsley wrote:
> > On Wed, Aug 12, 2009 at 9:18 AM, Ary Borenszweig
> > wrote:
> >> This compiles and runs in D2:
> >>
> >> --
> >> import std.stdio;
> >>
> >> auto foo() {
> >>return 1;
> >> }
> >>
> >> void main() {
> >>writefln("%s", foo());
> >> }
I've recently convinced myself that nullability should be the exception instead
of the norm. So much of the code I write in C#/D uses reference objects
assuming they're non-null. Only in certain special cases do I handle null
explicitly. The issue is that if any special case is missed/mishandled
Andrei Alexandrescu Wrote:
> Jason House wrote:
> > DIPs
> > shared
> > debugger support
> > arrays
>
> You'll be soon surprised regarding literally all of the above. But I
> don't want to speak again on Walter's behalf :o).
>
> Andrei
> >> Or, like so many other features in D, leave it half-specified,
> >> half-useful, and half-implemented because "it got too hard"?
> >
> > Which features of D are you referring to?
>
> Design by Contract
> "Order of declaration doesn't matter"
> Protection level enforcement of various kinds
>
Walter Bright Wrote:
> Having optional parentheses does lead to unresolvable ambiguities. How
> much of a problem that really is is debatable, but let's assume it
> should be resolved. To resolve it, a property must be distinguishable
> from a regular function.
I have not been following the p
Walter Bright Wrote:
> Currently, that can't be done. But it would be good to get it in for D2.
> The question is, what rule to use?
My vote would be to use partial ordering [1] for consistency. I'm just not sure
what that would mean in this situation :(
[1]
http://dobbscodetalk.com/index.ph
Andrei Alexandrescu Wrote:
> grauzone wrote:
> >> This is *exactly* why I said DIPs need to have some form of editorial
> >> control.
> >
> > I agree. DIPs shouldn't just be "newsgroup postings with higher
> > exposure". At least we'd need a higher entry barrier, like some checking
> > for form
Andrei Alexandrescu Wrote:
> I suggest anyone who wants to do something for D to focus on the
> installation aspect. It's a relatively well-defined project of high
> importance and high visibility. We simply can't afford to introduce D to
> the world without a state-of-the-art installation proc
Sadly, this has been the writing on the wall for some time. For me, the
critical question for D2 is "How will unique be handled?". Andrei favors a
library-based struct-only solution (Where structs with non-immutable
pointers/references are disallowed)
I'm surprised to hear that Bartosz's owners
Other, less technical items:
A clear and "finalized" spec. If it isn't implemented, it should be yanked
(or clearly marked as pending)
A plan for library support. Not just Tango, but also Phobos. D1 Phobos could
not evolve.
Don Wrote:
> A lot of frustration has been expressed on the newgrou
if you don't plan on owning the DIP, why did you write it up? Any half-hearted
proposal is doomed to failure.
Brad Roberts Wrote:
> For grins (and to see how well this process might work), I lifted a bugzilla
> issue (177) into a DIP:
>
>http://www.prowiki.org/wiki4d/wiki.cgi?LanguageDevel/
that's a great choice for DIP 2. it addresses the really old "return const"
issue. We know Walter at one time wanted to solve the issue and we have an
official record of Andrei saying it's technically sound.
The sample usage should probably include temporary variables inside a function.
What
Lars T. Kyllingstad Wrote:
> Leandro Lucarella wrote:
> >
> > [1] http://www.prowiki.org/wiki4d/wiki.cgi?DiPs
> > [2] http://www.prowiki.org/wiki4d/wiki.cgi?DiP1
> >
>
>
> I think this is a good idea. :) Regarding the template, I think there
> should be one more section, called "Description".
bearophile Wrote:
> This page shows the proposed changes for the next version of Haskell:
> http://hackage.haskell.org/trac/haskell-prime/wiki/Status
>
> I like how the Haskell community is well organized in such things.
>
> Bye,
> bearophile
IIRC, Andrei asked in D.announce if anyone could set
Christian Kamm wrote:
> Jason House wrote:
>> there's already someone working on getting that patch into gdb. I've been
>> trying lately to play with the dmd -gc output so that gdb recognizes it
>> properly. I'm not very far, and my queries in #gdb have gone
Walter Bright Wrote:
> Jason House wrote:
> > there's already someone working on getting that patch into gdb.
>
> Great!
>
> > I've
> > been trying lately to play with the dmd -gc output so that gdb
> > recognizes it properly.
>
> dumpobj
Walter Bright Wrote:
> Jason House wrote:
> > Silence is frequently mistaken for apathy. Responses to bug reports
> > generate a lot of good will and encourages further help from the
> > community. Bugs open for years with no comments have the opposite
> > effect...
Walter Bright Wrote:
> Jason House wrote:
> > Walter Bright Wrote:
> >
> >> My general experience with posted compiler patches is about half of them
> >> are good, the other half are incorrect and require more
> >
> > for the bad half, do you comme
Walter Bright Wrote:
> My general experience with posted compiler patches is about half of them
> are good, the other half are incorrect and require more
for the bad half, do you comment in the bug reports about why you think the
patches are bad?
Walter Bright Wrote:
> Jason House wrote:
> > Walter Bright Wrote:
> >
> >> If there's more I can do to make this work, I would like to know
> >> what that is.
> >
> > I know D does not burden itself with backwards compatibility,
>
>
Walter Bright Wrote:
> If there's more I can do to make this work, I would like to know what
> that is.
I know D does not burden itself with backwards compatibility, but the lack of
compatibility has to affect many D projects. There are many D1-only projects
that can't be used within D2. When
Kagamin Wrote:
> yigal chripun Wrote:
>
> > there is no defined system for the development of D. even MS has a well
> > defined plan for their .net platform. where's the plan for D? where the
> > process to define that plan?
> > Either you need to have a plan or you need to have a community dr
Eric Poggel Wrote:
> I don't have D2 installed, but the above fails to compile in d1
> (non-constant expression __dgliteral1).
Here's the code I use in D2:
R delegate(T) toDelegate(R, T...)(R function(T) f){
return delegate R(T t){return f(t);};
}
> - I'm probably biased on this, and trying to rationalize it as more of a
> "new user experience" issue than it really is, but the regex engine's been
> broken with open tickets for a while now. Ok, maybe not truly broken, but
> buggy enough that I haven't felt comfortable trusting it. Again,
Tim Matthews Wrote:
> Paul D. Anderson wrote:
> > A. What I'm looking forward to in the near future:
> >
> > 1) D2 will be frozen.
>
>
>
> I am really for having Bartosz Milewski's changes implemented in D2
> rather than d3, or further. Multi core cpus are here now and it would
> help D get
What happens when #3 turns up an inconsistency in the language spec after #1
and #2 have occurred? It'd be a real shame to have to wait another 2-3 years
for it to be corrected in a stable DMD!
If #4 hits issues, #1 may block resolution of those issues.
#6 won't occur after #1 either. If histor
Qian Xu Wrote:
> Release and Debug are two configuration sets.
>
> FEATURE | DEBUG | RELEASE
> ---+---+-
> assertion | |
> ---+---+-
> invariant | |
> ---+---+-
> debug symbols | |
> -
Qian Xu Wrote:
> Hi All,
>
> "invariant" is a great language feature of D. But nice thing costs.
>
> Is it possible to make it compiler switchable? Like "dmd --ignore-invariant"
> or "dmd --version=ignore-invariant" It think it will be quite helpful to
> generate test version and release versio
bearophile Wrote:
> Jason House:
> >Many functions in Phobos are not marked as pure even though they could be.
> >That limits pure's use for me)<
>
> If you list them then Walter may later fix Phobos.
I did file an entry I'm bugzilla for std.cpuid. It was
Jeroen Dirks Wrote:
> Does anyone know the answer to this D related question on SO?
>
> http://stackoverflow.com/questions/1008803/how-to-use-pure-in-d-2-0/
addMsg is not marked pure and pure functions can't call impure functions... I'm
not sure if addMsg can be marked pure or not. It does not
grauzone Wrote:
> Daniel Keep wrote:
> >
> > davidl wrote:
> >> The runtime vararg push into stack with align of 4, however programmer
> >> might neglect this easily and cause problem.
> >>
> >> ...
> >>
> >
> > That's because you're not supposed to do that.
> >
> > std.stdarg
>
> Contains onl
Don Wrote:
> Saaa wrote:
> >> Why can't this be in official Phobos1?
> >> It's a ploy from the D2 camp, right? :)
> >
> >> If by "ploy" you mean "Walter's official stance not to change D1 or
> >> Phobos 1," then yes, it's a ploy. But that's a bit harsh, no?
> > I fixed it to how I meant it.
> >
Bartosz Milewski Wrote:
> Why don't you wait for part 3 (coming this week) which talks about templates.
> You'll find it simpler than you'd expect. Let's not fight the strawman. I'm
> also working on the tutorial.
Are you replying to me or the original poster? I thought I said I wanted to
wait
Mike L. Wrote:
> The following code compiles fine for me with dmd 1.043:
At least for closures, D2 will catch this type of issue. I doubt such escaping
stack frame issues will get addressed in D1. Either way, you should submit a
bugzilla entry.
>
> --
> module wtf;
>
> version(Tan
Nick B Wrote:
> Jason House wrote:
> > Bartosz's latest blog implies he's settled on a design. I'm curious if that
> > means dmd 2.031 will finally contain the critical changes for that.
> >
> > If I understand the blog cirrectly, the design (in a
Sean Kelly Wrote:
> Jason House wrote:
> > Andrei has stated previously that unique was left out of the type system
> > because it added little value to the const system. Now that shared and
> > multithreading are here, unique has more value.
> >
> > I hav
Andrei has stated previously that unique was left out of the type system
because it added little value to the const system. Now that shared and
multithreading are here, unique has more value.
I have two basic questions:
1. What would make unique difficult to add?
2. What benefits do you forsee
Fractal wrote:
> Hello
>
> if I have the following code:
>
> int foo;
> foo = 5;
>
> When the variable foo is declared, it is initialized to int.init, or has
> garbage contents until it is assigned?
>
> Thanks
D will always initialize variables unless you explicitly tell it not to.
(although
Andrei Alexandrescu wrote:
> If we want to allow people to create ranges that are classes (as opposed
> to structs) the requirement for a save() function is a must. This is
> because copying class ranges with
>
> Range copy = original;
>
> only creates a new alias for original; the two share the
Over in D.anounce, the LDC devs said they would have an easier time upgrading
to newer dmd (fe) versions if the source was in source control. Even if Walter
is the only one with write access, it's still be helpful. It's helpful for more
than just the LDC folks; that's just the most recent exampl
BCS Wrote:
> Reply to Jason,
>
> > My hobby project is a multi-threaded game-playing AI. My current
> > scheme uses a shared search tree using lockless updates with search
> > results.
> >
>
> As in threaded min-max? Have you got anything working? I known from
> experience
> that this ones a
Bartosz Milewski Wrote:
> Jason House Wrote:
>
> > Bartosz Milewski Wrote:
> >
> > My hobby project is a multi-threaded game-playing AI. My current scheme
> > uses a shared search tree using lockless updates with search results.
> > Besides general abil
Bartosz Milewski Wrote:
> Leandro Lucarella Wrote:
>
> > BCS, el 28 de mayo a las 15:57 me escribiste:
>
> >
> > Maybe, I'm just saying why I don't comment on D2 concurrency model. I find
> > it too complex for my needs (i.e. for what I know, I won't give my opinion
> > about things I don't kno
Tim Matthews Wrote:
> Jason House wrote:
> > I'm really surprised by the lack of design discussion in this thread. It's
> > amazing how there can be huge bursts of discussion on which keyword to use
> > (e.g. manifest constants), but then complete silence about m
the first place?
This seems really unfair to Walter. Then again, I see no indication of Walter
wanting anything else.
Jason House Wrote:
> The article implies some level of flow analysis. Has Walter come around on
> this topic?
>
> As far as considering a variable moved, I beli
Tim Matthews Wrote:
>
> This may seem slightly OT but in your blog "I will use syntax similar to
> that of the D programming language, but C++ and Java programmers
> shouldnt have problems following it."
>
>
> class MVar {
> private:
> T_msg;
> bool _full;
> public:
> // p
The article implies some level of flow analysis. Has Walter come around on this
topic?
As far as considering a variable moved, I believe the following should be
reasonable
Any if statement (or else clause) containing a move
Any switch statement containing a move for any case
Any fall-throu
Bartosz Milewski wrote:
> The post is back, rewritten and with some code teasers.
We've been teased for 6 months or more. I'm hoping the details will come
out quickly now!
Here's what I took away from the article:
* Goal is to have minimal code changes for single threaded code
* unique and le
Andrei Alexandrescu Wrote:
> Don wrote:
> > Andrei Alexandrescu wrote:
> >> I think you can't do better. Complexity is O(n) at a minimum because
> >> you need to go through each element. The heap-based algorithm has O(n
> >> log m). What you could improve on is the log m factor (m = the number
Andrei Alexandrescu Wrote:
> Jason House wrote:
> > Don't get offended, he didn't respond to anyone else's algorithm either.
>
> I just wanted to bring what I think is an interesting problem to the
> table; my response shouldn't be used as a yardstick
Georg Wrede Wrote:
> Andrei Alexandrescu wrote:
> > Georg Wrede wrote:
> >> Andrei Alexandrescu wrote:
> >>> This is somewhat OT but I think it's an interesting problem. Consider
> >>> the following data:
> >>>
> >>> double[][] a =
> >>> [
> >>> [ 1, 4, 7, 8 ],
> >>> [ 1, 7 ],
> >>> [
nobody Wrote:
> Hi,
>
> I'm writing a data processing program in D, which deals with large amounts of
> small objects. One of the thing I found is that D's GC is horribly slow in
> such situation. I tried my program with gc enable & disabled (with some manual
> deletes). The GC disabled version (
grauzone Wrote:
> Daniel Keep wrote:
> >
> > grauzone wrote:
> >> ...
> >>
> >> Now the irony is, that Wlater wouldn't even allow Debian to redistribute
> >> a properly packaged dmd... (if Debian wanted to)
> >
> > Speak ye of the evil Wizard Wlater, previous servant of the dark empire
> > of Sy
Stewart Gordon Wrote:
> Jason House wrote:
>
> > That is unfortunately a rather sticky point. The in operator does not
> > return bool. I think the lack of !in is to encourage writing of efficient
> > code. I'm not really sure though.
>
> How, exa
Andrei Alexandrescu Wrote:
> I'm writing a range to select a random sampling of a forward range. The
> number of elements in the forward range is already known.
>
> The strategy is: at any moment, I know I need to select k random samples
> out of n. To implement popFront, I generate a random nu
Andrei Alexandrescu Wrote:
> This is somewhat OT but I think it's an interesting problem. Consider
> the following data:
>
> double[][] a =
> [
> [ 1, 4, 7, 8 ],
> [ 1, 7 ],
> [ 1, 7, 8],
> [ 4 ],
> [ 7 ],
> ];
>
> We want to compute an n-way union, i.e., efficiently sp
Andrei Alexandrescu wrote:
> grauzone wrote:
How about giving these up to Tango? The only problem is, it has not
been ported to D2 yet.
>>>
>>> That's not an option.
>>
>> Licensing reasons? Not-Invented-Here-Syndrome? You love reinventing the
>> wheel?
>
> Licensing and the love for r
would complain
about any attempt to clean it up. For smaller tweaks (such as where to move
something), I put it into category 3 since little stuff is more likely to
generate opinions.
Andrei Alexandrescu wrote:
> Jason House wrote:
>> What do you / others consider the weakest / missin
Andrei Alexandrescu Wrote:
> Jason House wrote:
> > BCS wrote:
> >
> >> Hello Jason,
> >>
> >>> Should the final freezing of D2 be delayed until major D1 libraries
> >>> port to D2? I'm mostly thinking of Tango, but I bet there are ot
Steven Schveighoffer wrote:
> No, you need a pointer. If T is a reference type, how do you distinguish
> a null element from the end of the iteration?
Do you have any common cases where a range would generate nulls as part of
its normal output? I think using the natural null feature of referen
Robert Clipsham wrote:
> My main thought is that this is a bit early to be thinking about this.
> D2 is still in alpha, with lots of feature and bug changes in each
> release. Until its feature set begins to settle I don't think it is too
> important to think about how to manage a release.
I get
BCS wrote:
> Hello Jason,
>
>> Should the final freezing of D2 be delayed until major D1 libraries
>> port to D2? I'm mostly thinking of Tango, but I bet there are others.
>> It may even be good if major libraries could use a Phobos-compatible
>> license and become part of the releases by digital
Jeremie Pelletier wrote:
> Why is there no !in operator just like there is a !is operator?
> Is it because this expression evaluates to a pointer to the found element?
> Even so, it would make asserts much easier to write.
That is unfortunately a rather sticky point. The in operator does not
re
dsimcha wrote:
> == Quote from Jason House (jason.james.ho...@gmail.com)'s article
>> Andrei has indicated that the current plan is to finalize D2 when his
>> book comes
> out.
>> Given this, I'm interested in what _community_ activity should be done as
>&
Andrei has indicated that the current plan is to finalize D2 when his book
comes out.
Given this, I'm interested in what _community_ activity should be done as part
of this.
Should there be a formal review and polishing of the D spec? More than just
criticizing faults, people should submit pa
bearophile Wrote:
> bearophile:
> > Having a return also helps to see templates as closer to compile-time
> > functions (changing few things there may be ways to merge the syntax of
> > templates with the syntax of compile time functions, reducing the
> > complexity of D).<
>
> To write some t
Robert Clipsham Wrote:
> I recently came across this:
>
> version( BackendFoo ) {}
> else version( BackendBar ) {}
> else version( BackendCar ) {}
> else
> {
>pragma( msg, "Warning: backend version undefined" );
>pragma( msg, "Attempting to guess backend" );
>version( Windows )
>{
Georg Wrede Wrote:
>
> --- Disclaimer: this is a bit long. Read it later. ---
Wow, you're right. Sadly, I stopped reading about 80% through (discussion on D4)
At a high level, I agree with your assessment about an easy growth path for
newbors to gurus. I should also add that a language must ma
Georg Wrede Wrote:
> Jason House wrote:
> > I no longer try to work out the details and merely hope my efforts
> > plant a seed for thought. It's far less frustrating that way.
>
> Sadly, ( /thoroughly/ sadly), this is like a party group. If you really
> want exp
Steven Schveighoffer Wrote:
>
> The thread discussing what to do for input ranges vs. forward ranges got
> me thinking.
>
> The range concept may be defined backwards in terms of which is more
> specialized. Consider that an input range is always usable as a stream.
> But a stream is not
dsimcha Wrote:
> == Quote from Jason House (jason.james.ho...@gmail.com)'s article
> > dsimcha Wrote:
> > > == Quote from Jason House (jason.james.ho...@gmail.com)'s article
> > > > IMHO, D should have a type with low size and function call overhead &
Andrei Alexandrescu Wrote:
> MLT wrote:
> > I think that if
> >> R last = r;
> > then after
> >> r.popFront;
> > the order of elements in "last" should not change, no matter what
> > type of range you are dealing with. (That means that input operations
> > would be buffered to the leftmost range t
Bill Baxter Wrote:
> On Wed, May 20, 2009 at 4:03 PM, dsimcha wrote:
> > == Quote from Jason House (jason.james.ho...@gmail.com)'s article
> >> IMHO, D should have a type with low size and function call overhead > like
> >> a
> > struct as
dsimcha Wrote:
> == Quote from Jason House (jason.james.ho...@gmail.com)'s article
> > IMHO, D should have a type with low size and function call overhead > like a
> struct as well as reference semantics like a class.
>
> What's wrong with a pointer to a heap-allo
Bill Baxter Wrote:
> On Wed, May 20, 2009 at 12:05 PM, dsimcha wrote:
> > == Quote from Bill Baxter (wbax...@gmail.com)'s article
> >> On Wed, May 20, 2009 at 11:44 AM, Andrei Alexandrescu
> >> wrote:
> >> > Jason House wrote:
> >> >>
dsimcha Wrote:
> == Quote from Bill Baxter (wbax...@gmail.com)'s article
> > On Wed, May 20, 2009 at 11:44 AM, Andrei Alexandrescu
> > wrote:
> > > Jason House wrote:
> > >>
> > >> Andrei Alexandrescu Wrote:
> > >>
> >
Andrei Alexandrescu Wrote:
> Jason House wrote:
> > I feel like there are too many differences between input and forward
> > ranges for such a minor difference. Many range functions are written
> > assuming no side effects on the caller. This can restrict the use of
> &g
I feel like there are too many differences between input and forward ranges for
such a minor difference. Many range functions are written assuming no side
effects on the caller. This can restrict the use of helper functions. It may be
best to make their usage different...
Andrei Alexandrescu W
bearophile Wrote:
Andrei Alexandrescu:
> I don't plan to discuss minor features on this group anymore.
That's a real pity.
I had a lot of respect for you and your perpetual inclusion of the D community
(both announcing features and getting design feedback).
Very early on in this thread, it be
Andrei Alexandrescu Wrote:
> Bill Baxter wrote:
> > On Mon, May 18, 2009 at 3:29 PM, Jason House
> > wrote:
> >
> >> It's all a matter of perspective. I see both as begin .. end. That may be
> >> the same reason why I think addition when I see fo
Andrei Alexandrescu Wrote:
> Jason House wrote:
> > Andrei Alexandrescu Wrote:
> >
> >> Jarrett Billingsley wrote:
> >>> On Mon, May 18, 2009 at 1:46 PM, Andrei Alexandrescu
> >>> wrote:
> >>>
> >>>> Final switch works
>
> > On a similar note, Andrei, what is this spree of removing features? Ok some
> > are obviously bad, imaginary types for example, but why remove other stuff
> > such as commplex and with?
>
> TDPL is coming out. This is quite literally the last chance to shed some
> old skin. Complex as a b
Andrei Alexandrescu Wrote:
> Jarrett Billingsley wrote:
> > On Mon, May 18, 2009 at 1:46 PM, Andrei Alexandrescu
> > wrote:
> >
> >> Final switch works with enums and forces you to handle each and every value
> >> of the enum. Regular switch gets ranged cases by the syntax case a: .. case
> >> b
grauzone Wrote:
> Robert Fraser wrote:
> > Jason House wrote:
> >> Andrei Alexandrescu Wrote:
> >>
> >>> Consider:
> >>>
> >>> foreach (x; 1.0 .. 4.1) writeln(x);
> >>> foreach_reverse (x; 1.0 .. 4.1) writeln
201 - 300 of 486 matches
Mail list logo
