May 03, 2013 Re: DConf 2013 last talk | ||||
---|---|---|---|---|
| ||||
Posted in reply to Steven Schveighoffer | On 2013-05-03 08:32, Steven Schveighoffer wrote: > Microphones were provided for all questions (and facebook even provided > staff that ran microphones to people who asked them, along with a mixing > engineer to cut down on feedback and adjust the level of the mics to the > speaker's voice level/distance to mic). I would say if the videos turn > out to be anything but spectacular, I'd be surprised. That sounds great. Can't wait for the videos :) -- /Jacob Carlborg |
May 03, 2013 Re: DConf 2013 last talk | ||||
---|---|---|---|---|
| ||||
Posted in reply to Arlen | > 2. Are we going to spend the next 10-20 years writing garbage collectors for D?
Good question, what's with the GC from last years GSoC?
|
May 03, 2013 Re: DConf 2013 last talk | ||||
---|---|---|---|---|
| ||||
Posted in reply to David | On Friday, 3 May 2013 at 11:38:38 UTC, David wrote:
>> 2. Are we going to spend the next 10-20 years writing garbage collectors for D?
>
> Good question, what's with the GC from last years GSoC?
From what I understand (which could be completely incorrect) the author disappeared when GSoC ended, so it was never pulled in.
|
May 03, 2013 Re: DConf 2013 last talk | ||||
---|---|---|---|---|
| ||||
Posted in reply to Joseph Cassman | On 5/2/13 5:11 PM, Joseph Cassman wrote: > On Thursday, 2 May 2013 at 23:59:48 UTC, Andrei Alexandrescu wrote: >> I'll answer community questions in my last talk at DConf 2013, which >> is about 24 hours from now. Please send yours here or on Twitter #dconf. >> >> Andrei > > If you could provide an update on the allocators design and > implementation -- progress and/or roadmap -- that would be great. Also > if there are any plans to update std.container as a result. I will touch on this. > Are there any plans to incorporate some of the ideas in the two talks > about GC at the conference (or other ideas regarding GC)? I'll probably get to this only informally; there's been some discussion elsewhere. > What are the plans for ARM short or long-term? Will try to discuss. Andrei |
May 03, 2013 Re: DConf 2013 last talk | ||||
---|---|---|---|---|
| ||||
Posted in reply to Andrei Alexandrescu | Any plans or roadmap on including a GUI lib in phobos? Is it 5 years away? 10 years? Never? |
May 03, 2013 Re: DConf 2013 last talk | ||||
---|---|---|---|---|
| ||||
Posted in reply to sk | My journey using GUI libs is as follows: 1. Started using DWT lib (old one, when it was still supported) 2. DWT was abandoned, so I moved to DFL, tinkered with min-win etc 3. DFL is abondened now? ... moved to GTKD 4. GTKD is good, but API is hard to understand (atleast for me) 5. DWT is supported again, so move back to DWT 6. ??? |
May 03, 2013 Re: DConf 2013 last talk | ||||
---|---|---|---|---|
| ||||
Posted in reply to d coder | On 5/2/13 9:10 PM, d coder wrote:
> And another one. I am working on an embedded DSL on top of D Language. I
> am using compile time parser ctpg https://github.com/youkei/ctpg for
> some syntax parsing. It works great, expect for memory footprint of the
> compiler which makes it impractical to parse any 1000+ lines of code at
> compile time.
>
> So the question is -- What are the plans to optimize the compiler from
> memory perspective?
This is an important issue. I'll touch on it only at a higher level when discussing quality of implementation.
Andrei
|
May 03, 2013 Re: DConf 2013 last talk | ||||
---|---|---|---|---|
| ||||
Posted in reply to Sergei Nosov | On 5/2/13 11:02 PM, Sergei Nosov wrote: > On Thursday, 2 May 2013 at 23:59:48 UTC, Andrei Alexandrescu wrote: >> I'll answer community questions in my last talk at DConf 2013, which >> is about 24 hours from now. Please send yours here or on Twitter #dconf. >> >> Andrei > > What are the plans regarding "functional part" of the language? > > 1) It seems the standard library would benefit from implementing > functional alternatives to every statement (e.g. foreach, switch, etc.). > There are some more interesting functions (like "tap" which was > discussed on this NG not so long ago) Probably I won't discuss this because it's a very new idea. > 2) @pure functions - attribute inferring (feasible? good idea? going to > be implemented in some way?) and optimizations (is there any good > showcases right know? what's the potential? what's planned?) I'll try to touch on attribute inference. Thanks! Andrei |
May 03, 2013 Re: DConf 2013 last talk | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jacob Carlborg | On 5/2/13 11:22 PM, Jacob Carlborg wrote: > On 2013-05-03 01:59, Andrei Alexandrescu wrote: >> I'll answer community questions in my last talk at DConf 2013, which is >> about 24 hours from now. Please send yours here or on Twitter #dconf. > > Could you say something about the general development process of D, how > the future of that looks like. > > * Are we getting any stable branch/releases that there's been talking > about? I will discuss this. > * Are we done with the surprise commits/features? I'm thinking of UDA's This as well. > * Perhaps something about the DIP's. Now they just sitting there doing > nothing This too. Andrei |
May 03, 2013 Re: DConf 2013 last talk | ||||
---|---|---|---|---|
| ||||
Posted in reply to Peter Alexander | On 5/3/13 12:38 AM, Peter Alexander wrote: > On Thursday, 2 May 2013 at 23:59:48 UTC, Andrei Alexandrescu wrote: >> I'll answer community questions in my last talk at DConf 2013, which >> is about 24 hours from now. Please send yours here or on Twitter #dconf. > > 1. How do you plan to solve the const postblit problem? i.e. the problem > that you cannot create a const copy of a struct since the postblit > constructor cannot be run on non-mutable objects. Is the solution to > introduce C++-style copy constructors? Probably won't go to this level of detail. Depends on time. > 2. What, in your opinion (and Walter's), are the top issues with D that > are hindering uptake? I will talk about our largest weaknesses. > 3. What do you believe are D's biggest weaknesses that will likely > remain unresolved by design? (*real* weaknesses, not just temporary > shortcomings) Fundamentally we're a compiled language building on C's memory bedrock. That setup has innate strengths and weaknesses. Of course, we've added our own blunders to all that and there are limitations to what you get to express in D. But I see our largest problems solvable through design (and one such design emerged at this conference). Andrei |
Copyright © 1999-2021 by the D Language Foundation