Re: Release D 2.099.1
On Tuesday, 12 April 2022 at 22:06:36 UTC, sunshine wrote: On Friday, 8 April 2022 at 09:33:47 UTC, Sebastiaan Koppe wrote: > On Thursday, 7 April 2022 at 21:32:34 UTC, Martin Nowak wrote: >> Glad to announce D 2.099.1, ♥ to the 12 contributors. >> >> http://dlang.org/download.html >> >> This point release fixes a few issues over 2.099.0, see the >> changelog for more details. >> >> http://dlang.org/changelog/2.099.1.html >> >> -Martin > > Getting signature errors. > > ``` > $ curl -fsS https://dlang.org/install.sh | bash -s dmd > Downloading and unpacking > http://downloads.dlang.org/releases/2.x/2.099.1/dmd.2.099.1.linux.tar.xz > 100.0% > gpg: Signature made Thu Apr 7 16:35:02 2022 UTC > gpg:using EDDSA key > 27637885C3CF8350732A1CA5723DC8887F97C07F > gpg: Can't check signature: No public key > Invalid signature > http://downloads.dlang.org/releases/2.x/2.099.1/dmd.2.099.1.linux.tar.xz.sig > ``` Mr. Nowak had a key expired in March and has made a new one. The fingerprints were/are F46A10D0AB44C3D15DD65797BCDD73FFC3EB6146 (rsa4096 2020-03-12 [SC] [expired: 2022-03-12]) F8A26D5D7572ECA06EC7973182C52E37A8BC8393 (ed25519 2022-03-22 [SC] [expires: 2024-03-21]) The latter I think signs the release and can be fetched with id 82C52E37A8BC8393 How to retrieve this key? I tried gpg --recv-keys 82C52E37A8BC8393 and gpg --keyserver keyserver.ubuntu.com --recv-keys 82C52E37A8BC8393 No luck with either. The resulting error for both is: gpg: keyserver receive failed: Network is unreachable What is the correct --keyserver for the public keys used to verify these binaries? Thanks
Re: DConf 2020 Canceled
to all the people dogpiling the responses against Era's point of view: the reason there is not more dissent, whether here or in other respectable forums (eg scientific research in general), is purely because of social mechanics (ostracization of dissenters) - not the inherent unassailable truthfulness of the apparent consensus point of view. when contrary information is personally and professionally radioactive, is it a wonder nobody wants to associate themselves with it? but here, as in so many elsewheres, "this is not the place." I'm already pushing the boundary with this meta-post containing no specific assertions, and will almost certainly put Mike in the unfortunate position of having to put his foot down in this thread (sorry Mike). I'm just pointing out that, anywhere that people's real life identities are tied to what they are saying, there will be an artificial consensus around safe, socially sanctioned viewpoints. so you all essentially get an unrestricted platform to say "lol we're so informed and naysayers are tinfoil-hat nutters," but if somebody made a good-faith effort to respond to any of your points, messages would start getting deleted and the thread would be locked. and far from exceptional, that happens EVERYWHERE. I don't expect any of you /respectable, rational/ people to read it, but for the shy dissenters among us, here's a short little essay on the circularity of scientific peer review (I am not the author): https://www.reddit.com/r/accountt1234/comments/5umtip/scientific_circular_reasoning/
Re: Developer positions at Sociomantic Labs
“The best minds of my generation are thinking about how to make people click ads.” - Jeffrey Hammerbacher (Cloudera cofounder)
Re: Project Highlight: The New CTFE Engine
On Friday, 18 November 2016 at 10:59:11 UTC, Mike Parker wrote: If you've been following Stefan's CTFE Status thread here in the forums, you know some of the details of the work he has been doing in overhauling the CTFE engine. In a post targeting the world at large, he explains why he started the project, describes the deficiencies he found with the current implementation, and gives a high level overview of his new one. The blog post: https://dlang.org/blog/2016/11/18/project-highlight-the-new-ctfe-engine/ Reddit: https://www.reddit.com/r/programming/comments/5dltm4/a_look_at_the_overhaul_of_ds_ctfe_engine/ there is a typo after the first quote: fourms
Re: Release D 2.072.0
On Monday, 7 November 2016 at 18:26:44 UTC, Anonymous wrote: On Monday, 31 October 2016 at 01:27:08 UTC, Martin Nowak wrote: Glad to announce D 2.072.0. http://dlang.org/download.html This is the release ships with the latest version of dub (v1.1.0), comes with lots of phobos additions and native TLS on OSX. See the changelog for more details. http://dlang.org/changelog/2.072.0.html -Martin It seems that there was another regression that nobody detected, because nobody has build one of the major tool used by most of the D enthusiastic: https://github.com/Hackerpilot/DCD/issues/352 https://issues.dlang.org/show_bug.cgi?id=16663 To be honest, I know that the D world existed before me, and I know that it'll still exist if I leave. Between, 2.072 is the worst release I've ever seen.
Re: Release D 2.072.0
On Monday, 31 October 2016 at 01:27:08 UTC, Martin Nowak wrote: Glad to announce D 2.072.0. http://dlang.org/download.html This is the release ships with the latest version of dub (v1.1.0), comes with lots of phobos additions and native TLS on OSX. See the changelog for more details. http://dlang.org/changelog/2.072.0.html -Martin It seems that there was another regression that nobody detected, because nobody has build one of the major tool used by most of the D enthusiastic: https://github.com/Hackerpilot/DCD/issues/352 https://issues.dlang.org/show_bug.cgi?id=16663
Re: Release D 2.072.0
On Wednesday, 2 November 2016 at 15:08:26 UTC, anonymous wrote: On Wednesday, 2 November 2016 at 12:36:45 UTC, Johan Engelen wrote: LDC built with DMD 2.072.0 gives the following error when run: object.Error@src/rt/minfo.d(356): Cyclic dependency between module ddmd.traits and ddmd.cond ddmd.traits* -> ddmd.attrib -> ddmd.cond* -> ddmd.expression -> ddmd.traits* Pretty much all of LDC's D code is DDMD front-end code, master is at front-end version 2.071.2. I hope someone can try to build DMD 2.071.2 using 2.072.0 and see if a similar issue is found. I confirm, dmd 2.072 can't build dmd 2.071.2, same error, but boot since master straping works there's probably something that's been fixed in one or two of these ddmd modules, likely a static ctor... Maybe after this: https://github.com/dlang/dmd/commit/1d0ab8b9c136e46bf449c506ca25d2c8a784f7b9#diff-b4674e7b5d3a44178526afdefc9aa368 ddmd.attribs was removed https://github.com/dlang/dmd/commit/1d0ab8b9c136e46bf449c506ca25d2c8a784f7b9#diff-b4674e7b5d3a44178526afdefc9aa368L15 and it was also part of the cycle.
Re: Release D 2.072.0
On Wednesday, 2 November 2016 at 12:36:45 UTC, Johan Engelen wrote: LDC built with DMD 2.072.0 gives the following error when run: object.Error@src/rt/minfo.d(356): Cyclic dependency between module ddmd.traits and ddmd.cond ddmd.traits* -> ddmd.attrib -> ddmd.cond* -> ddmd.expression -> ddmd.traits* Pretty much all of LDC's D code is DDMD front-end code, master is at front-end version 2.071.2. I hope someone can try to build DMD 2.071.2 using 2.072.0 and see if a similar issue is found. I confirm, dmd 2.072 can't build dmd 2.071.2, same error, but boot since master straping works there's probably something that's been fixed in one or two of these ddmd modules, likely a static ctor...
Re: Do D need a popular framework? like ruby's rails? or java 's ssh?
On 19.01.2016 14:22, beck wrote: Do D need a popular framework? in china ,a little peopel use dlang. i just use it do some simple work for myself. yet,i have learn d for a week .. i ask so many friends ,they don't use D at all.we use golang more than dlang. Please don't post questions or suggestions like this to the Announce group. The announce group is for software releases, book publications, stuff like that. The General group would have been the right place for this.
Re: Logo for D
On 17.01.2016 18:55, Karabuta wrote: Ohh! A great design is better seen by a designer. "Iron with steal, steel with gold, gold with diamond". Always room for improvement. I don't understand.
Re: Logo for D
On 16.01.2016 18:55, karabuta wrote: How do you see it? http://amazingws.0fees.us/wp-content/uploads/2016/01/dlang2.png Many variants are on the way. Do you intend to propose this for the official logo? If so, be aware that the logo is a delicate matter. There have been various proposals to change it from the current one, and all have been rejected. It's Walter himself who is rather strictly against any changes. I have been pushing for this variant: https://gist.github.com/aG0aep6G/0803ec5ae49f6afb0196 You see it's very, very similar to the current one. To the point that you could say it's really the same logo. Yet, it was the one part of the red-top-bar redesign that didn't fly with the powers that be. I haven't given up yet, though. By the way, I'm not sure if this is announcement material. If you're looking for feedback, I think the General group would have been a better fit.
Re: Better docs for D (WIP)
On 07.01.2016 14:31, Andrei Alexandrescu wrote: Here's a simple idea we can implement rather quickly. Say a user is browsing https://dlang.org/builtin.html and find a typo. They press a button labeled "Fix typo". That opens https://github.com/D-Programming-Language/dlang.org/edit/master/builtin.dd. From there people can edit the source file to fix the typo and create a PR, all without leaving the browser or building the documentation. We have this already. Top right corner, "Improve this page". People are using the feature occasionally.
Re: Please vote for the DConf logo
On 14.11.2015 13:07, Alix Pexton wrote: I have a personal dislike of narrow D glyphs, so I'd like to move the swoosh a small distance from the spire to add a horizontal hint to the outline. I think the text could be closer to the glyph, and higher, such that the D is in about the 2-o'clock position on the swoosh, which I think would reflect the Dlang logo more strongly. Like so? https://gist.github.com/anonymous/e33f3354ff534fe7d99d I think a wider stylized D works well. I'm not a fan of moving the text closer and up, though. So I'd prefer this: https://gist.github.com/anonymous/ba5018d0091744e00f8b If I didn't quite capture what you had in mind, the SVG is handwritten and rather simple, maybe try tinkering with it yourself.
Re: Please vote for the DConf logo
On 13.11.2015 15:22, Andrei Alexandrescu wrote: By my count: * 1.1:xxx * 1.2:xxx * 2: xxx * 3: xx * 3, change font: xxx So 3 by "anonymous" is it! Whee! As I said in the original post, I'm not much of a designer. So if anyone wants to improve details, I wouldn't mind. But I myself won't be able to improve much upon it, probably. This also applies to the font. I just browsed through the local list, which is probably just the Ubuntu defaults, and picked one that looked good to me. I'm not attached to it by any means, and I don't know the first thing about fonts. So if anyone has something better in mind, go for it. The D in "DConf" is currently bold. Unbolding it may be an option. I like it, though. I created https://github.com/D-Programming-Language/dconf.org/pull/94 and also preemptively uploaded the logo to http://dconf.org/2016/index.html. Had to adjust svg dimensions to 200x110. I/we should make an SVG version that uses paths instead of , so that it doesn't depend on a local font. Maybe agree on the font first, though.
Re: Please vote for the DConf logo
On Wednesday, 4 November 2015 at 09:30:30 UTC, Andrei Alexandrescu wrote: Reply to this with 1.1, 1.2, 2, or 3: 1) by ponce: Variant 1: https://github.com/p0nce/dconf.org/blob/master/2016/images/logo-sample.png Variant 2: https://raw.githubusercontent.com/p0nce/dconf.org/4f0f2b5be8ec2b06e3feb01d6472ec13a7be4e7c/2016/images/logo2-sample.png 2) by Jonas Drewsen: https://dl.dropboxusercontent.com/u/188292/g4421.png 3) by anonymous: PNG: http://imgur.com/GX0HUFI SVG: https://gist.github.com/anonymous/4ef7282dfec9ab327084 Thanks, Andrei 1.1
Re: DConf 2016, Berlin: Call for Submissions is now open!
On 04.11.2015 01:41, Andrei Alexandrescu wrote: So, while I'm away (I'll be traveling for most of this week), please let's vote on the two DConf logo proposals and choose one for http://dconf.org. I think you've missed mine which makes it three. 1) by ponce: Variant 1: https://github.com/p0nce/dconf.org/blob/master/2016/images/logo-sample.png Variant 2: https://raw.githubusercontent.com/p0nce/dconf.org/4f0f2b5be8ec2b06e3feb01d6472ec13a7be4e7c/2016/images/logo2-sample.png 2) by Jonas Drewsen: https://dl.dropboxusercontent.com/u/188292/g4421.png 3) by me: PNG: http://imgur.com/GX0HUFI SVG: https://gist.github.com/anonymous/4ef7282dfec9ab327084
Re: Beta D 2.069.0-b1
On Thursday 08 October 2015 06:14, extrawurst wrote: > `The -property switch has been deprecated.` Does that mean > @property has no effect anymore ? Yes. I've made a pull request to mention that (and put a note on the spec page). https://github.com/D-Programming-Language/dlang.org/pull/1119 We should probably try to finally find good semantics for @property.
Re: Beta D 2.069.0-b1
On Thursday 08 October 2015 16:34, anonymous wrote:
> On Thursday 08 October 2015 06:14, extrawurst wrote:
>
>> `The -property switch has been deprecated.` Does that mean
>> @property has no effect anymore ?
>
> Yes.
Correction: @property has at least one effect without -property. typeof acts
differently on properties vs non-properties.
struct S
{
@property int p();
int n();
}
pragma(msg, typeof(S.init.p)); /* int */
pragma(msg, typeof(S.init.n)); /* int() -- i.e. a function */
I wasn't aware of this before Jonathan M Davis told me [1]. I don't think
it's specified anywhere, at least I can't find anything.
[1]
https://github.com/D-Programming-Language/dlang.org/pull/1119#issuecomment-146576866
Re: This Week in D: livestreaming and we're moving forward on Windows bindings!
On Monday 05 October 2015 21:29, Adam D. Ruppe wrote: > http://arsdnet.net/this-week-in-d/oct-04.html Quoting the the article: > which generates Microsoft format object files and the MS linker even on 32 bit I think you a word there. > past time pastime > avaiable available > D headers and separating concerns of implementation For the C/C++ converts, Misses a full stop, or a line break.
Re: This Week in D: livestreaming and we're moving forward on Windows bindings!
On Monday 05 October 2015 23:30, Andy Smith wrote: > On Monday, 5 October 2015 at 19:35:53 UTC, anonymous wrote: [...] >> Quoting the the article: > > 'the the' ???!!! hehe [...] >> I think you a word there. >> > > I think you a grammatical error there. That one was on purpose, just like yours. > > Honestly I think if you're going to pull people up on > grammar/spelling errors you really need to do yourself a favour > and not have the same type of error in your own post. It > undermines your case somewhat and, frankly, makes you look like a > bit of a dick. > > Apologies in advance if this was a well-meaning post but to be > honest the tone didn't seem that friendly. I don't think Adam minds my nagging. I hope he doesn't. I sure don't mean to berate anyone for making typos. I wouldn't point them out in a forum post. But TWID is like two or three steps up from that.
Re: reggae v0.5.0: new features in the D meta-build system
On Friday 25 September 2015 23:27, Atila Neves wrote: > How does one compile 3 files "at the same time" and generate 3 > object files? There was a reference to a -multiobj option in that > post but that's not even in the man page. dmd -c foo.d bar.d baz.d rdmd would probably do this by now, if it weren't for the template instantiation issue. There's a nice, simple example of the issue in the PR discussion: https://github.com/D-Programming-Language/tools/pull/170#issuecomment-112526734 > Even if it exists and works as I assume it does, it seems to me > to be a silly way to compile files. As Andrei mentioned at DConf > this year, the D idiom is to group source files per package when > compiling. That's what reggae does by default for D files. It > just works. Aside from the template instantiation issue, I don't see how doing a package at a time is better than compiling exactly those files that need to be compiled.
Re: reggae v0.5.0: new features in the D meta-build system
On Saturday 26 September 2015 01:24, Atila Neves wrote: > There have been threads about this before. It turns out that > compiling per file is usually slower than compiling the whole > package/app at once. It's not intuitive, but it's true (I > measured it myself). reggae has an option to compile per-file but > I haven't used it since switching to per-package once. Compiling one file at a time is yet another thing. 1) Compile everything into one object file: dmd -c -ofresult.o foo.d bar.d 2) Compile to multiple object files in one run: dmd -c foo.d bar.d 3) Compile to multiple object files in multiple runs: dmd -c foo.d; dmd -c bar.d Since you didn't know about 2, I take it that you measured 1 vs 3. 3 is bound to be slower when the modules share dependencies, because they have to be parsed again and again. 2 may be faster or slower than 1, I don't know, a quick check didn't show a difference. When the template instantiation issue ever gets fixed, I wouldn't be surprised if 2 got slower than 1. Of course, any slowness of 2 must then be weighed against 1 compiling more than necessary.
Re: Beta D 2.068.2-b1
On Thursday, 10 September 2015 at 03:38:31 UTC, Martin Nowak wrote: Due to a regression in 2.068.1 we'll directly follow up with an unplanned point release 2.068.2. This is the beta for that point release. http://downloads.dlang.org/pre-releases/2.x/2.068.2/ Please test any of your code against this beta to help finding bugs. https://issues.dlang.org/ -Martin I tested a vibe.d project and got lots of linker errors starting with ../../.dub/packages/vibe-d-0.7.24/libvibe-d.a(libevent2_38e3_5d7.o): In Funktion `_D4vibe4core7drivers9libevent215Libevent2Driver6__ctorMFNbC4vibe4core6driver10DriverCoreZC4vibe4core7drivers9libevent215Libevent2Driver': [path]../../.dub/packages/vibe-d-0.7.24/source/vibe/core/drivers/libevent2.d:97: Nicht definierter Verweis auf `event_set_mem_functions' I'll try to investigate this tonight. I am not an expert in linker issues, but looks like libevent is not properly linked in. The project builds with 2.068.0. vibe.d 0.7.24 dub 0.9.22 (I'll try to update) linux x86_64
Re: Beta D 2.068.2-b1
On Thursday, 10 September 2015 at 09:56:40 UTC, wobbles wrote: Maybe try running dub build --force (to make it rebuild all of vibes dependencies also. Might solve it... no effect:(
Re: Beta D 2.068.2-b1
On Thursday, 10 September 2015 at 11:44:42 UTC, anonymous wrote: On Thursday, 10 September 2015 at 09:56:40 UTC, wobbles wrote: Maybe try running dub build --force (to make it rebuild all of vibes dependencies also. Might solve it... no effect:( After uninstalling dmd 2.068 andinstalling the .deb package instead of downloading+extracting the tar.xz everything works fine!
Re: Release D 2.068.1
On Monday 07 September 2015 00:32, Martin Nowak wrote: > http://downloads.dlang.org/releases/2.x/2.068.1/ Trying to download the 7z Windows file gives me a 403. http://downloads.dlang.org/releases/2015/dmd.2.068.1.windows.7z
Re: 1st Ever Artificial Consciousness to be Written in D Language
On Sunday, 6 September 2015 at 09:42:53 UTC, Grand_Axe wrote: On Wednesday, 2 September 2015 at 21:13:12 UTC, anonymous wrote: On Wednesday, 2 September 2015 at 14:41:20 UTC, GrandAxe wrote: Unnetworked personal mobile devices are the target platform for the standard implementation of OBI. What hardware/OS (if any) will you use? Depending on the answer: do you plan to submit PR to extend plattform support of the compiler as necessary? Compared to your agenda full D support on Android/iOS/bare metal may be easy... Anyway a large codebase may be a good compiler test for ARM (or whatever you use). A final target platform has not yet been settled, the main thrust right now is for a successful demo. However phone OS's such as Android (especially) and iOS have the potential to throw up nightmare security issues, therefore might not be candidates. Also the platform will need to be unnetworked which might knock out phone OS's. The demo will be PC based, after which it will be optimised for a number of target processors. Summary: 1. OBI uses big data 2. no network 3. portable Conclusion: OBI runs on a portable device with sufficient resources to process big data in realtime (I want OBI to answer immediately) - no laptop. I am looking forward for such a device - I want it as least as fast as a XEON cpu, 32 GB+ RAM and a battery life of at least several hours. I guess your demo will be some kind of console-based ELIZA. "emacs -> M-x doctor" is quite good:)
Re: 1st Ever Artificial Consciousness to be Written in D Language
On Wednesday, 2 September 2015 at 14:41:20 UTC, GrandAxe wrote: Unnetworked personal mobile devices are the target platform for the standard implementation of OBI. What hardware/OS (if any) will you use? Depending on the answer: do you plan to submit PR to extend plattform support of the compiler as necessary? Compared to your agenda full D support on Android/iOS/bare metal may be easy... Anyway a large codebase may be a good compiler test for ARM (or whatever you use).
Re: Dynamic arrays
On Monday 31 August 2015 23:09, Minas Mina wrote: > I have started a series of tutorials in D. > > This is my latest blog post, which is about dynamic arrays: > http://minas-mina.com/2015/08/31/dynamic-arrays/ > > Constructive criticism is welcome. "Dynamic arrays are allocated on the garbage collected heap" "Dynamic arrays can be sliced" These are not wrong, but maybe a little bit misleading. Static arrays and pointers can be sliced, too. And a slice of a static array or pointer is ... dramatic pause ... a dynamic array that doesn't necessarily refer to the GC heap.
Re: Dynamic arrays
On Monday 31 August 2015 23:36, John Colvin wrote: > I prefer the term "slice" to dynamic array. Because it's an > unfamiliar term it helps prevent confusion for people who are > used to what other languages call dynamic arrays. I'm not a fan of the term "slice". Not because I dislike the word itself, but simply because the spec uses "dynamic array" for T[]. The "D Slices" article [1] on dlang.org uses "slice" for T[], and "dynamic array" for the underlying chunk of memory. It's no surprise that people get confused when the different pages of the site can't agree on which word to use for what. [1] http://dlang.org/d-array-article.html
Re: Build It And They Will Not Come
On Thursday 20 August 2015 17:18, Daniel wrote: Anyway, I didn't know about Ali's book. Maybe it could be linked at dlang.org's left menu? It's the first link on the Getting Started page (added somewhat recently). And it's the first link in the Books Articles section. I wouldn't oppose a link on the top level, but I'm not sure if it's a good idea.
Re: Programming in D paper book is available for purchase
On Wednesday, 19 August 2015 at 15:53:27 UTC, Luís Marques wrote: On Wednesday, 19 August 2015 at 00:57:32 UTC, Ali Çehreli wrote: [...] Ali, congratulations on releasing such a complete book on D! I know this took you an immense effort, as these things always do, but the results speak for themselves. It's a great book, and I hope you consider keeping it revised with a second edition. Also, I do like the cover, too :-). [...] Someone's already posted it! https://www.reddit.com/r/programming/comments/3hllq0/programming_in_d_tutorial_and_reference_book_by/
Re: Release D 2.068.0
On Monday, 10 August 2015 at 15:41:39 UTC, Dominikus Dittes Scherkl wrote: Maybe the state should reflect this progress better, because these 3000 open and unassigned bug give a much worse impression of the state of D than the language really is in. People get easy turned away from D by that look, which I think would be easy to avoid. Yeah, we don't really make use of the ASSIGNED status. Maybe we should. I assigned the issues for which I have open pull requests to myself. But that's only 3 issues. I don't know how to get the heavy hitters to be more attentive in that regard. I guess whenever one makes a pull request to fix an issue, the issue can be considered to be assigned to them. You could go through everything and assign issues to PR makers, but that'd be quite some legwork.
Re: DCD 0.7.0-alpha1
On Saturday, 8 August 2015 at 00:19:38 UTC, Brian Schott wrote:
https://github.com/Hackerpilot/DCD/releases/tag/v0.7.0-alpha1
DCD is an IDE and editor-independent autocompletion system for
the D programming language.
Release notes are available at the above link.
0.7.0 has some major changes to its internal structure, so
please help me to test it.
So far, so good. However i've found a way to crash the server
even if it's a very laughable and unrealistic case; it crashes
dmd too BTW.
---
struct Foo {
int a;
this(int a) { this.a = a; }
static immutable Foo bar = Foo(1);
}
void main() {
auto a = Foo.bar;
import std.stdio;
writeln(a.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar
.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar
.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar
...
.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar.bar
}
---
if you repeat the access chain .bar.bar etc, let's say 16X per
line, for 4000X lines and try a dot completion then the server
crashes.
Re: Release D 2.068.0
On Monday, 10 August 2015 at 12:24:36 UTC, Dominikus Dittes Scherkl wrote: Congrats, but why are there still 6 Regressions / 34 Blockers open in Bugzilla? At least with the one that opens from the main D page /resouces/bugtracker. Is this a different tracker that's not up to date? Regarding regressions: I think the policy is to not release with new regressions. That is, regressions from before 2.068 don't block the release. Regarding blockers: As far as I know, blocker doesn't mean a thing for releases. I think many of those have been labeled blocker because they block someone in their work, rather than blocking a release.
Re: DCD 0.7.0-alpha1
On Saturday, 8 August 2015 at 00:19:38 UTC, Brian Schott wrote: https://github.com/Hackerpilot/DCD/releases/tag/v0.7.0-alpha1 DCD is an IDE and editor-independent autocompletion system for the D programming language. Release notes are available at the above link. 0.7.0 has some major changes to its internal structure, so please help me to test it. I'd like to test, particularly under Win, but std.experimental.allocator (+ std.meta) are still not merged. If I understand correctly it means that DCD 0.7 will not be easily buildable until next pre-release (2.069-alpha)...in 2 monthes !
Re: DCD 0.7.0-alpha1
On Saturday, 8 August 2015 at 02:25:29 UTC, Joakim Brännström wrote: On Saturday, 8 August 2015 at 01:32:50 UTC, anonymous wrote: I'd like to test, particularly under Win, but std.experimental.allocator (+ std.meta) are still not merged. If I understand correctly it means that DCD 0.7 will not be easily buildable until next pre-release (2.069-alpha)...in 2 monthes ! Brian made it easy for us, std.experimental.allocator is in the submodule containers. std.meta is part of 2.068. So it works with dmd-2.068.0-rc1, successful compilation :) Thanks for the information. So Everything is fine. Windows users that are used to buid with the bat file (because Digital Mars make doesn't accept the makefile) should get an updated version soon.
Re: Changelog
On Wednesday, 5 August 2015 at 19:04:29 UTC, Brian Schott wrote: Where does that changelog come from? I made some pull requests against a file that I thought was the changelog to document some Phobos changes that got merged, but now I don't see it on dlang.org. https://github.com/D-Programming-Language/dlang.org/pull/1028/files https://github.com/D-Programming-Language/dlang.org/pull/1027/files Your stuff has been moved to the 2.069 section: https://github.com/D-Programming-Language/dlang.org/blob/8bb4b6ea3699f4061d86dcb26459149d45a2958e/changelog.dd#L5-L16 hasUDA seems to be in 2.068, so that should be moved back to the 2.068 section. getUDAs and getSymbolsByUDA don't seem to have made it, so they're correctly commented out for now.
Re: Beta D 2.068.0-b2
On Monday, 27 July 2015 at 23:40:28 UTC, anonymous wrote: On Monday, 27 July 2015 at 09:04:08 UTC, Martin Nowak wrote: On 07/26/2015 11:13 PM, anonymous wrote: Is std.expermimental.allocator planned for 2.068 ? I see it's still not merged and we already almost in August. We're trying hard here to meet some deadlines, so things are really simple. If something is ready (reviewed, tested, documented, and merged into stable) it'll end up in a release, otherwise it'll end up in the next release (only 2 month later). We can't postpone indefinitely just b/c every other person is trying to push through their particular interests. Yep I see where the energy goes http://forum.dlang.org/thread/ckjukjfkgrguhfhkd...@forum.dlang.org where it' gone
Re: Beta D 2.068.0-b2
On Monday, 27 July 2015 at 23:49:34 UTC, anonymous wrote: On Monday, 27 July 2015 at 23:40:28 UTC, anonymous wrote: On Monday, 27 July 2015 at 09:04:08 UTC, Martin Nowak wrote: On 07/26/2015 11:13 PM, anonymous wrote: [...] We're trying hard here to meet some deadlines, so things are really simple. If something is ready (reviewed, tested, documented, and merged into stable) it'll end up in a release, otherwise it'll end up in the next release (only 2 month later). We can't postpone indefinitely just b/c every other person is trying to push through their particular interests. Yep I see where the energy goes http://forum.dlang.org/thread/ckjukjfkgrguhfhkd...@forum.dlang.org where it' gone where it's gone. Instead to solve the conflicts...
Re: Beta D 2.068.0-b2
On Saturday, 25 July 2015 at 12:21:19 UTC, Martin Nowak wrote: Second beta for the 2.068.0 release. Is std.expermimental.allocator planned for 2.068 ? I see it's still not merged and we already almost in August.
Re: LDC 0.15.2 beta2 is out!
On Tuesday, 7 July 2015 at 06:10:33 UTC, Mathias Lang wrote: Congrats ! Though, I don't know if you'd notice, but those binary are not using from Travis-ci: https://github.com/rejectedsoftware/vibe.d/pull/1171#issuecomment-119005076 Which makes it sensitively harder to test it (and I'd like to thank Martin Nowak again for making it so easy to test compilers - testing a beta compiler is now one additional line to .travis.yml, commit, push). I reported [1] yesterday. Most probably some tests in vibe.d will segfault (my simple http file server crashes upon the first request on linux-x86_64). Great that vibe.d tests with beta versions. If someone can confirm [1], it will not hurt :) [1] https://github.com/ldc-developers/ldc/issues/989
Re: forum.dlang.org, version 2 (BETA)
On Thursday, 4 June 2015 at 15:04:05 UTC, Vladimir Panteleev wrote: http://beta.forum.dlang.org/ Many major and minor improvements. Some major ones: - dlang.org theme, fully responsive and mobile-friendly - keyboard navigation in all views - automatically saved post drafts - get notified of new posts and replies with subscriptions - full text search - by persistent request, a new view mode (vertical-split) - post to mailing lists - even faster, believe it or not. This update is the sum of 256 commits over 34 days of development. Cool! * No threaded view? * Space to scroll doesn't work. * How about being able to collapse/expand quotes?
Re: This Week in D: DConf 2015 Wednesday Morning writeups!
The link to harbored is broken ... On Tuesday, 2 June 2015 at 04:22:08 UTC, Adam D. Ruppe wrote: On Tuesday, 2 June 2015 at 04:17:47 UTC, John Colvin wrote: Actually, http://forum.dlang.org/post/sujyaurgyfumoiimi...@forum.dlang.org would be better cool fixed, remember to refresh as the file is aggressively cached.
Re: Quick Start with D: few examples and set of links.
Yes, that works. I also tried what John Colvin suggested
(.byLine(KeepTerminator.no, std.ascii.newline) and that works
too. Is it true that both of those are better than adding chomp
because it would be one less time through the pipeline?
Learned several new things today! Thanks again!
On Friday, 1 May 2015 at 15:03:33 UTC, Ilya Yaroshenko wrote:
On Friday, 1 May 2015 at 14:01:38 UTC, Anonymous wrote:
This is great, thank you.
I couldn't get the example in the introduction to work without
adding .map!(chomp) to the pipeline:
auto sample = File(10numbers.txt)
.byLine
.takeExactly(10)
.map!(chomp)
.map!(to!double)
.tee!((x){mean += x;})
.array;
Without that, I got an error converting to a double (my file
had '\r' after each number)
On Friday, 1 May 2015 at 08:18:10 UTC, Ilya Yaroshenko wrote:
http://d.readthedocs.org
I hope this examples will be useful for students.
Ilya
`parse` should works with whitespace after number:
auto sample = File(10numbers.txt)
.byLine
.takeExactly(10)
.map!(line = parse!double(line))
.tee!((x){mean += x;})
.array;
Re: Gource visualisations of various D repositories
On Tuesday, 23 December 2014 at 17:33:07 UTC, Gary Willoughby wrote: For a bit of fun and prompted by a thread requesting such, i've created a few visualisation videos generated from D repositories by Gource. DMD: https://www.youtube.com/watch?v=8OuZ9sfyEbI Phobos: https://www.youtube.com/watch?v=5OLccv4FhE8 Druntime: https://www.youtube.com/watch?v=JHdbdnBVXus Tools: https://www.youtube.com/watch?v=E6aXnB5iAco Dub: https://www.youtube.com/watch?v=eCl0TQRvZqY Gource: https://code.google.com/p/gource/ Have fun! Thanks for spending the time to make them :) It's totally trivial but worth to see, mostly dmd and Phobos.
Re: Sargon component library now on Dub
On Sunday, 14 December 2014 at 13:31:57 UTC, disapoint wrote: On Sunday, 14 December 2014 at 03:26:56 UTC, Walter Bright wrote: http://code.dlang.org/packages/sargon These two modules failed to generate much interest in incorporating them into Phobos, but I'm still rather proud of them :-) Here they are: ◦sargon.lz77 - algorithms to compress and expand with LZ77 compression algorithm ◦sargon.halffloat - IEEE 754 half-precision binary floating point format binary16 I'll be adding more in the future. how about you take the time to add a complete set of window headers before more people loose customers or their reputation? Everything is in the lib file... it takes 30 second to copy and convert the import header from MSDN. I mean: your attack is not relevant. By the way additional imports could be added by PR by anyone tough I'm not sure if the DM team accept 3rd party PR (?).
Re: Programming in D book, draft of the first print edition and eBook formats
Thx, your book's just helped me last night (opSlice template not well explained in the official html). Two questions: - do you know that your website has serious design issue ? - does paper version mean no more free pdf/ebook ?
Re: D for the Win
On Thursday, 21 August 2014 at 01:51:11 UTC, ketmar via Digitalmars-d-announce wrote: i always wonder how good people at finding various offences I'm not offended. and fascims everywhere. It's pretty much the Nazi anthem. It doesn't get much more fascist than that. Of course, someone can play with fascist phrases without being a fascist or promoting fascism. As I said, coming from an Israeli, it's probably benign. If the author was German, I'd feel uneasy about it. And don't tell me that Germans carelessly throwing around Nazi slogans isn't something to feel uneasy about. The NPD (Nazi party) is in two Landtagen (state parliaments). i bet that such people are glad to censor I'm not trying to censor anything. Neither am I convinced that banning Nazi symbols, songs, etc (as we do in Germany) is the right way to go. I think I'd rather have the Nazis wear Hakenkreuz armbands than other, obscure symbols that I can't identify. It's not like they stop existing when we ban their uniforms.
Re: D for the Win
On Wednesday, 20 August 2014 at 22:57:21 UTC, Paulo Pinto wrote: As a Portuguese living in Germany, I would say not everyone knows that outside Germany. Certainly. As I said, from an Israeli it's probably benign. I guess if aynthing, it's meant to be jokingly provoking towards Germans. I don't mind that at all.
Re: D for the Win
Dlang Dlang Über Alles as a German, O_O
Re: D for the Win
On Wednesday, 20 August 2014 at 21:43:26 UTC, Walter Bright wrote: On 8/20/2014 2:33 PM, anonymous wrote: Dlang Dlang Über Alles as a German, O_O I'm not surprised that the German programming community has taken to D. After all, German cars all have those D stickers on them :-) No, no, Dlang Dlang Über Alles is a take on Deutschland Deutschland über alles (Germany Germany over everything), the first verse of the national anthem as sung in Nazi times. I was actually worried if the author is German. He's not, thankfully. He's from Israel. From a German author that would be an embracement of fascism. Coming from an Israeli, I don't really know where to put it, probably completely benign.
