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

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.

Are there any plans to incorporate some of the ideas in the two talks about GC at the conference (or other ideas regarding GC)?

What are the plans for ARM short or long-term?

Thanks!

Joseph

On Fri, May 3, 2013 at 5:41 AM, Joseph Cassman <jc7919@outlook.com> wrote:

> 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.
>

+1

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? I know that the GC is disabled at compile time to make
the compiler as fast as possible. Can we think about adding a switch to dmd
to optionally enable the GC? This is not going to change the
functional behavior of the compiler and so we can give an option to the
end-user to enable the switch when compile time footprint is becoming an
issue.

Regards
- Puneet

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)

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?)

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?

* Are we done with the surprise commits/features? I'm thinking of UDA's

* Perhaps something about the DIP's. Now they just sitting there doing nothing

Oh, and if it's not too late. Make sure there are microphones for the audience for the questions. If that's not available, it's important that the speaker (or someone) repeats the questions for the recording. Hurb Sutter is really good at this but otherwise it seems the recoding are mostly forgotten.

-- 
/Jacob Carlborg

On Thu, 02 May 2013 23:22:01 -0700, Jacob Carlborg <doob@me.com> wrote:

> Oh, and if it's not too late. Make sure there are microphones for the audience for the questions. If that's not available, it's important that the speaker (or someone) repeats the questions for the recording. Hurb Sutter is really good at this but otherwise it seems the recoding are mostly forgotten.

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.

-Steve

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?

2. What, in your opinion (and Walter's), are the top issues with D that are hindering uptake?

3. What do you believe are D's biggest weaknesses that will likely remain unresolved by design? (*real* weaknesses, not just temporary shortcomings)

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

Are there any chances at seeing more design focus on hardcore embedded needs? Something about make D usage there possible not only in theory, but also in practice. Stuff like silently allocating language features and stdlib, excessive TypeInfo's, fat runtime etc. Some of those issues are already being addressed by pull requests but bug picture is still not clear.

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 design decisions in language and/or phobos, that are now more or less 'carved in stone', would you like to have differently?

On Thu, May 2, 2013 at 6:59 PM, Andrei Alexandrescu <SeeWebsiteForEmail@erdani.org> 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


1. How many years must pass before GCC includes a front end for D?
2. Are we going to spend the next 10-20 years writing garbage collectors for D?

Arlen