C# 4.0: Meet the Design Team | Charles

Galo

Well would there be a UCFirst and IsNumeric this time ? hahahaha Smiley

just kidding, keep up the good work guys

rbougha

Impatiently waiting for this version of C#.

strawhat

Charles (I mean the Charles who wrote the post (as in the one who signed his name (you know Charles))),

You forgot to close one of your '('s

Charles
Welcome Change

In reply to strawhat

#Jul 15th, 2008 @ 7:59 PM

Yes. Indeed, sentence composition could stand to gain from a better compiler.

Thanks for testing Smiley

C

beetle

ff

Ananth B

Very cool discussion. I like that fact that a large focus for C# 4.0 is concurrency. I've been doing a lot of work on LINQ and concurrency (with the Brahma project http://brahma.ananthonline.net). I feel what I'm trying to do is exactly what a part of the discussion was about, which is: introducing a model that allows developers to write code that runs in parallel, without them having to put in a whole bunch of thought. The limitations of query expressions fit very well into a streaming-computation model, which is the feature I've tried to exploit. It is also possible to interleave code that runs on another processor with code that runs on the CPU (an architecture suitable for asymmetric core computing).

Even if included as language features, I feel a LINQ-like provider based model (which allows users to write their own providers) would allow the most flexibility since multi-core processor development is going to be in flux around the time C# 4.0 might be released. Allowing people to decide the model of concurrency to be used, while supporting basic constructs (I feel COmega has some very nifty ideas there). It is also entirely possible that the "scalar" processors we run some part of the code on, may not be x86 (Tesla?).

In all, this is the perfect direction for C# to be heading in. But please, pretty please(?) give us, the developers ways to extend and control this beast's innards.

nyinyithann

Could you please tell me where i can get the transcript?
Thanks.

stevo_
Human after all

In reply to nyinyithann

#Jul 22nd, 2008 @ 5:59 AM

I was wondering today if theres any plans to improve the expression support for the compiler.. currently the compiler only accepts lambdas that are trees where a branch is a call to the next.. which makes it impossible to "bake" statement blocks..

It seems to me that the ability to have statement blocks as expressions could be very powerful, for example; you could have an expression as the handler for an enumerator, this could be useful for tools like linq to sql.. because you could do analysis against the expression, and determine which properties are being used.. and thus you could optimize the query to return just the fields that should be called..

I know that example isn't a guarentee, there would be rules about unsafe code still, and you would still need control over this optimization happening or not.. but thats just an example of things that could happen..