Re: std.signal : voting has begun
On Wed, Jan 15, 2014 at 9:35 PM, Russel Winder rus...@winder.org.uk wrote: We can, of course, now open the debate as to whether the Oxford Comma should be used. ;-) And does English mean American English, Canadian English, Australian English, South African English, New Zealand English, or proper English, i.e. that spoken in England. :-) -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder I vote: British English sentence construction with either American English or British English spelling. People are welcome to fix the documentation if the original writer's English is not 100% :) or if they just prefer the spelling to be from one of the other versions of English. Disclaimer: I speak South African English. P.S. I think Programming English is pretty much American English. For example is there any API that contains the English word Colour?
Re: std.signal : voting has begun
On Wednesday, 15 January 2014 at 15:59:20 UTC, qznc wrote: On Wednesday, 15 January 2014 at 07:46:29 UTC, Andrei Alexandrescu wrote: yada yada yada I just created a wiki page to document requirements. Hopefully, this helps people to decide on their vote and not to forget aspects. http://wiki.dlang.org/Phobos_Quality Should this be linked from http://wiki.dlang.org/Review/Process ? It will be great if we will have a list of English-speaking people that can help with documentation. For example, English is not my native language, so it will be great if somebody else read and correct my documentation. So, we need a list of people who interested to help with documentation for new modules with their contact information (e-mail should be enough).
Re: std.signal : voting has begun
Thanks for helping to keep voting threads clean from off-topic discussions.
Re: std.signal : voting has begun
On 1/15/14 11:35 AM, Russel Winder wrote: On Wed, 2014-01-15 at 13:42 -0500, John J wrote: […] Uses complete english sentences with correct syntax, grammar, and punctuation. Please capitalize the e in english. We can, of course, now open the debate as to whether the Oxford Comma should be used. ;-) At ACCU I attended talks by you, an awful speaker, and an incompetent chowderhead. Now you tell me whether we should use the Oxford comma or not :o). And does English mean American English, Canadian English, Australian English, South African English, New Zealand English, or proper English, i.e. that spoken in England. :-) We can always aspire... Andrei
Coming back, Unique, opDot and whatever else
Hello everyone! It's been a long time since I last posted here, I've been away from all things D, only being able to take an occasional peek from time to time. It's so good to be back. I'm now finding a bit of time to commit to learn D, more relearn as it would seem. I've started my rediscoveries with exploring of concurrency, parallelism, threading in D, and after some time I found myself thinking I need a unique encapsulator. Don't ask why, I may not even be able to answer it in a month. But that helped me solve some problems before in C++, so I thought why not try it here? In a couple of page views I came upon std.typecons and its Unique type. And I thought why that is exactly what I want!. And it was, too. But after taking a closer look at its general implementation I just couldn't help myself but think well, it seems it was done in a hurry, never finished, left as it was because this of that and whatnot. I mean, those sparse comments, things like doesn't work yet, etc... I thought well, since I'm learning the language again, why not make it an exercise and fill those blanks? It'd certainly help me, because it would improve the abstraction I'm using, and because it's a learning experience. So, here's what I came up with for now: http://codepad.org/S4TfIdxc Granted, not a complete implementation, keeping not very far from the original. But right now I think it's a good time to ask you guys what do you think? Where have I went wrong, what did I do incorrectly, what potential issues can you spot in this? I mean, I'm not asking about using opDot(), which, as I understand it, could be going away anytime now. At least I think I managed to fill in most of the blanks of the current implementation while keeping (almost?) to the same interface. In short, please destroy this with Big Fat Phazerz so I could take the remaining ashes and contemplate on the next iteration :)
Re: Coming back, Unique, opDot and whatever else
Oh woops, it seems I misclicked the links and ended up posing in .announce instead of .learn. Sorry about that! If this is in any way movable, I'd be obliged. Thanks!
Re: Coming back, Unique, opDot and whatever else
On Friday, 17 January 2014 at 01:12:04 UTC, Stanislav Blinov wrote: Hello everyone! It's been a long time since I last posted here, I've been away from all things D, only being able to take an occasional peek from time to time. It's so good to be back. I'm now finding a bit of time to commit to learn D, more relearn as it would seem. I've started my rediscoveries with exploring of concurrency, parallelism, threading in D, and after some time I found myself thinking I need a unique encapsulator. Don't ask why, I may not even be able to answer it in a month. But that helped me solve some problems before in C++, so I thought why not try it here? In a couple of page views I came upon std.typecons and its Unique type. And I thought why that is exactly what I want!. And it was, too. But after taking a closer look at its general implementation I just couldn't help myself but think well, it seems it was done in a hurry, never finished, left as it was because this of that and whatnot. I mean, those sparse comments, things like doesn't work yet, etc... I thought well, since I'm learning the language again, why not make it an exercise and fill those blanks? It'd certainly help me, because it would improve the abstraction I'm using, and because it's a learning experience. So, here's what I came up with for now: http://codepad.org/S4TfIdxc Granted, not a complete implementation, keeping not very far from the original. But right now I think it's a good time to ask you guys what do you think? Where have I went wrong, what did I do incorrectly, what potential issues can you spot in this? I mean, I'm not asking about using opDot(), which, as I understand it, could be going away anytime now. At least I think I managed to fill in most of the blanks of the current implementation while keeping (almost?) to the same interface. Improving Phobos code by filling in the blanks is usually a good idea and a good learning experience as well. Changing an interface in Phobos is a big deal and should be thoroughly justified. Does it break backwards compatibility? Why is it necessary? (btw moving to .learn is not possible, unfortunately)
Re: Coming back, Unique, opDot and whatever else
On 2014-01-17 02:12, Stanislav Blinov wrote: Hello everyone! It's been a long time since I last posted here, I've been away from all things D, only being able to take an occasional peek from time to time. It's so good to be back. I'm now finding a bit of time to commit to learn D, more relearn as it would seem. I've started my rediscoveries with exploring of concurrency, parallelism, threading in D, and after some time I found myself thinking I need a unique encapsulator. Don't ask why, I may not even be able to answer it in a month. But that helped me solve some problems before in C++, so I thought why not try it here? In a couple of page views I came upon std.typecons and its Unique type. And I thought why that is exactly what I want!. And it was, too. But after taking a closer look at its general implementation I just couldn't help myself but think well, it seems it was done in a hurry, never finished, left as it was because this of that and whatnot. I mean, those sparse comments, things like doesn't work yet, etc... I thought well, since I'm learning the language again, why not make it an exercise and fill those blanks? It'd certainly help me, because it would improve the abstraction I'm using, and because it's a learning experience. So, here's what I came up with for now: http://codepad.org/S4TfIdxc Granted, not a complete implementation, keeping not very far from the original. But right now I think it's a good time to ask you guys what do you think? Where have I went wrong, what did I do incorrectly, what potential issues can you spot in this? I mean, I'm not asking about using opDot(), which, as I understand it, could be going away anytime now. At least I think I managed to fill in most of the blanks of the current implementation while keeping (almost?) to the same interface. In short, please destroy this with Big Fat Phazerz so I could take the remaining ashes and contemplate on the next iteration :) opDot has been replaced with opDispatch [1] and alias this [2]. Why can't @safe be used, can you use @trusted instead? You should probably use template constraints for createUnique as well. As for coding style, especially if you're aiming for including in Phobos: * Function names never start with underscore and always starts with a lowercase letter * I would prefer the same for instance variables as well, but I know there are several cases in Phobos where instance variables starts with an underscore [1] http://dlang.org/operatoroverloading.html#Dispatch [2] http://dlang.org/class.html#AliasThis -- /Jacob Carlborg
