Re: Calypso progress report (+ updated MingW64 build)
On Tuesday, 24 November 2015 at 22:51:40 UTC, Elie Morisse wrote: On Tuesday, 24 November 2015 at 06:44:31 UTC, deadalnix wrote: Yeah that's what I wanted to look int he IR. Where is _D_ZTISt9exception7__tiwrap defined ? Looks like you trimed the output :( Sorry I got a little heavy handed, here's the full IR: https://paste.kde.org/piivojs0s <3 <3 <3 <3
Re: [OT] bitcoin donation
On Monday, 23 November 2015 at 12:11:36 UTC, Steven Schveighoffer wrote: One could ask the same thing about any currency that isn't the one accepted at a store. I looked with a tinge of fascination at what bitcoin was a while ago. I think there is a natural averse reaction to something that is valuable but that you cannot understand. Don't be confused. Krugman do not understand bitcoin, but Krugman think that terrorism and riots are good, that the internet will never work and that there was no bubble in 2008, so I think is it fairly secure to ignore him. Many other economist have model that explain bitcoin's value. I know bitcoin has real math and genius behind it, and this is a silly example, but for those who do not understand how it actually works (including myself), it seems very similar in nature. Dollars (or whatever local currency you use) are understandable, and generally accepted at places where I shop. It's easy to see how one cannot duplicate them without evidence of doing so (the fundamental characteristic of currency). Online bits don't seem so uncopyable. -Steve Most people to not understand fractional reserve, bond emission, or how credit card works. I think that's ok. Back to the point, one of the value of bitcoin is to be able to transfer money internationally easily and for cheap. People that do have USD to spend on digital mars do not care. People abroad do care. Now I don't expect that accepting bitcoin will create a giant wave of donation, but, if anything, it is always good PR and not complicated. There is also no reason to refuse a donation or to make it more complex to do a donation. Andrei, Walter, if you need help to navigate the bitcoin ecosystem, you can reach me, I can help.
Re: New D book available for pre-order: D Web Development
On Wednesday, 29 July 2015 at 21:17:59 UTC, John wrote: On Wednesday, 22 July 2015 at 15:29:20 UTC, Kai Nacke wrote: my book D Web Development, available now for pre-order: https://www.packtpub.com/web-development/d-web-development Will this book be available in hardcopy ? Do you have a planned date for publication ?
Re: New D book available for pre-order: D Web Development
Any chance I could be added to the reviewers for this book? English is my primary language and I use vibe.d about 25 work hours a week. On Wed, Jul 22, 2015 at 5:29 PM, Kai Nacke via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote: > Hi all! > > Did you notice that development of LDC has been a bit slowly in the past? > The reason is my book D Web Development, available now for pre-order: > https://www.packtpub.com/web-development/d-web-development > > The story behind the book: > Some time after the review of the "D Cookbook" I was asked by Packt > Publishing if I would be interested in writing a book about web development > with D. By that time I used vibe.d only as a test case for LDC :-) But then > I took a closer look at the features of vibe.d and got enthusiastic about > it. I agreed to write the book. Hopefully the book shows much fun it is to > use D for web applications. > > For me writing a book is an incredible experience. It's challenging > because I am not a native English speaker. But I am having lot of fun in > exploring all the details, creating examples and writing about it. I > learned a lot in this process, including some more D programming. :-) > > A big thank to all (known and unknown) reviewers, to Andrei for > contributing the foreword and all others who helped in one way or the other. > > Having finished about 60% of the chapters, the other 40% and the rework > due to comments still absorb most of my time. Please be patient if fixing > LDC bugs takes some more time as usual. > > Regards, > Kai > >
Re: Calypso progress report (+ updated MingW64 build)
On Wednesday, 25 November 2015 at 01:04:19 UTC, deadalnix wrote: On Tuesday, 24 November 2015 at 22:51:40 UTC, Elie Morisse wrote: On Tuesday, 24 November 2015 at 06:44:31 UTC, deadalnix wrote: Yeah that's what I wanted to look int he IR. Where is _D_ZTISt9exception7__tiwrap defined ? Looks like you trimed the output :( Sorry I got a little heavy handed, here's the full IR: https://paste.kde.org/piivojs0s <3 <3 <3 <3 I can't find the runtime that goes with this. My best guess was here: https://github.com/Syniurge/druntime/blob/release-0.16.1/src/ldc/eh/common.d But it doesn't check the source language. Can I get some pointers ?
Re: Calypso progress report (+ updated MingW64 build)
On Tuesday, 24 November 2015 at 06:44:31 UTC, deadalnix wrote: Yeah that's what I wanted to look int he IR. Where is _D_ZTISt9exception7__tiwrap defined ? Looks like you trimed the output :( Sorry I got a little heavy handed, here's the full IR: https://paste.kde.org/piivojs0s
Re: [OT] bitcoin donation
On Monday, 23 November 2015 at 14:02:30 UTC, Joakim wrote: On Monday, 23 November 2015 at 12:11:36 UTC, Steven Schveighoffer wrote: One could ask the same thing about any currency that isn't the one accepted at a store. Sure, online is much less of a hassle, but it's still a little time to sign up and administer. Is that much of Ali's time worth spending for at least three donations, likely more? I bet it would be. I looked with a tinge of fascination at what bitcoin was a while ago. I think there is a natural averse reaction to something that is valuable but that you cannot understand. --snip-- I know bitcoin has real math and genius behind it, and this is a silly example, but for those who do not understand how it actually works (including myself), it seems very similar in nature. Dollars (or whatever local currency you use) are understandable, and generally accepted at places where I shop. It's easy to see how one cannot duplicate them without evidence of doing so (the fundamental characteristic of currency). Online bits don't seem so uncopyable. I'm by no means steeped in the tech, but it's pretty straightforward to understand the broad strokes. It's just a giant distributed ledger with some crypto to keep it secure and hashing to avoid double-counting, ie the duplication you're worried about. But ultimately that doesn't really matter, as almost nobody knows how Dollars or other local currencies are created or what makes them tough to copy either. ;) All that matters for a currency is that many buyers and sellers will accept it, or at least exchange it quickly and easily for your currency of choice, and bitcoin certainly passes that bar. Regimes vary in how they accommodate some kinds of financial innovation. If you're dealing with dollars anyway, that's one thing, but quite another if you have to figure out the peculiar local tax treatment (which may well not yet be determinate or written down anywhere). Plus in some places it might invite unwelcome scrutiny. So I agree that bitcoin is a very interesting technology, and this may be the real world application of an idea that goes back to the 90s of the new monetary economics (a book by cowen and kroszner), where the unit of account, medium of exchange, and store of value functions of money become unbundled. But its use unreasonable to expect people to behave in an optimising manner in every part of their lives, particularly when tax and regulation (and uncertainty surrounding them) get in the way.
Re: https everywhere!
On 11/24/2015 10:59 AM, David Nadlinger wrote: There are a number of issues with how SSL is set up on the server, from misconfiguration and/or outdated software: https://www.ssllabs.com/ssltest/analyze.html?d=dlang.org=on Compare this e.g. to issues.dlang.org, which achieves a solid A grade (although it uses a SHA-1 intermediary certificate, which will lead to issues soon): https://www.ssllabs.com/ssltest/analyze.html?d=issues.dlang.org=on Thanks, I forwarded this to Jan.
Re: [OT] bitcoin donation
On Wed, Nov 25, 2015 at 4:33 AM, deadalnix via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote: > On Monday, 23 November 2015 at 12:11:36 UTC, Steven Schveighoffer wrote: > >> One could ask the same thing about any currency that isn't the one >> accepted at a store. >> >> I looked with a tinge of fascination at what bitcoin was a while ago. I >> think there is a natural averse reaction to something that is valuable but >> that you cannot understand. >> >> > Don't be confused. Krugman do not understand bitcoin, but Krugman think > that terrorism and riots are good, that the internet will never work and > that there was no bubble in 2008, so I think is it fairly secure to ignore > him. > > Many other economist have model that explain bitcoin's value. > > I know bitcoin has real math and genius behind it, and this is a silly >> example, but for those who do not understand how it actually works >> (including myself), it seems very similar in nature. Dollars (or whatever >> local currency you use) are understandable, and generally accepted at >> places where I shop. It's easy to see how one cannot duplicate them without >> evidence of doing so (the fundamental characteristic of currency). Online >> bits don't seem so uncopyable. >> >> -Steve >> > > Most people to not understand fractional reserve, bond emission, or how > credit card works. I think that's ok. > > Back to the point, one of the value of bitcoin is to be able to transfer > money internationally easily and for cheap. People that do have USD to > spend on digital mars do not care. People abroad do care. > > Now I don't expect that accepting bitcoin will create a giant wave of > donation, but, if anything, it is always good PR and not complicated. There > is also no reason to refuse a donation or to make it more complex to do a > donation. > > Andrei, Walter, if you need help to navigate the bitcoin ecosystem, you > can reach me, I can help. > > :D anyone could accept donations to Ali on his behalf and then send him dollars whenever it reaches a certain value. Does the D Foundation have a bitcoin address?
Re: https everywhere!
On 11/24/2015 12:55 AM, Vladimir Panteleev wrote: This change could've been done with some community communication, no? Then we could've gone into this prepared. Jan just turned off the automatic http: => https: redirect. That will keep the site working as before giving time to get everything working with https: I ask that everything that doesn't work with https: get filed as a bugzilla issue. I've filed these: https://issues.dlang.org/show_bug.cgi?id=15378
Re: https everywhere!
On Monday, 23 November 2015 at 20:55:32 UTC, Walter Bright wrote: I'm pleased to announce that Jan Knepper has gotten us some proper certificates now, and dlang.org and digitalmars.com are now fully https! There are a number of issues with how SSL is set up on the server, from misconfiguration and/or outdated software: https://www.ssllabs.com/ssltest/analyze.html?d=dlang.org=on Compare this e.g. to issues.dlang.org, which achieves a solid A grade (although it uses a SHA-1 intermediary certificate, which will lead to issues soon): https://www.ssllabs.com/ssltest/analyze.html?d=issues.dlang.org=on — David
Re: https everywhere!
On Tuesday, 24 November 2015 at 18:59:39 UTC, David Nadlinger wrote: On Monday, 23 November 2015 at 20:55:32 UTC, Walter Bright wrote: I'm pleased to announce that Jan Knepper has gotten us some proper certificates now, and dlang.org and digitalmars.com are now fully https! There are a number of issues with how SSL is set up on the server, from misconfiguration and/or outdated software: https://www.ssllabs.com/ssltest/analyze.html?d=dlang.org=on Compare this e.g. to issues.dlang.org, which achieves a solid A grade (although it uses a SHA-1 intermediary certificate, which will lead to issues soon): https://www.ssllabs.com/ssltest/analyze.html?d=issues.dlang.org=on — David You're part of the bikscheder team.
Re: https everywhere!
On Tuesday, 24 November 2015 at 19:13:22 UTC, duff wrote: You're part of the bikscheder team. What is this even supposed to mean? — David
Re: let (x,y) = ...
On Tuesday, 24 November 2015 at 05:45:55 UTC, thedeemon wrote: Well, I believe it's a matter of taste. By allowing different number of elements there you allow more errors to sink in without gaining anything at all. You lose the choice between strict and loose operators, erase the difference. It's not the "consistency" I would like to have. ok, always curious about strategic choices, thanks :-)
Re: https everywhere!
On Monday, 23 November 2015 at 21:18:58 UTC, Walter Bright wrote: On 11/23/2015 1:11 PM, Adam D. Ruppe wrote: On Monday, 23 November 2015 at 20:55:32 UTC, Walter Bright wrote: I'm pleased to announce that Jan Knepper has gotten us some proper certificates now, and dlang.org and digitalmars.com are now fully https! So it isn't actually https everywhere. On a https page, the browsers by default block any external asset which itself isn't https loaded. The forum and TWID widgets are not https and now no longer load on the homepage :( The widgets don't, but the forums worked when I tried it. The forum widget isn't going to work until the forum is also HTTPS with a valid certificate. Sorry, I'm not going to pay for my own SSL certificate :) You'll either have to share, or wait until Let's Encrypt goes live and I get around to setting it up.
Re: https everywhere!
On Monday, 23 November 2015 at 20:55:32 UTC, Walter Bright wrote: I'm pleased to announce that Jan Knepper has gotten us some proper certificates now, and dlang.org and digitalmars.com are now fully https! Forcing HTTPS has broken: - The forum widget on the front page - This week's "This Week in D" excerpt on the front page - Runnable examples on the front page (more so than usual, now they are completely broken) Effectively our front page is now a broken mess. This change could've been done with some community communication, no? Then we could've gone into this prepared.
Re: https everywhere!
On Monday, 23 November 2015 at 20:55:32 UTC, Walter Bright wrote: I'm pleased to announce that Jan Knepper has gotten us some proper certificates now, and dlang.org and digitalmars.com are now fully https! Chrome warns me saying that dlang connectio is encrypted with obsolete cryptography
SuperStruct v0.2.0
For those that missed the first announcement
(http://forum.dlang.org/thread/jiucsrcvkfdzwinqp...@forum.dlang.org?page=1), SuperStruct is a struct that acts like a class; basically, a value type that exposes a common interface from its 'subtypes'.
Code on github: https://github.com/rcorre/superstruct
Anyways, I was having enough fun with this slightly ridiculous
idea to make a v0.20, so with no further ado, here's whats new:
Operators get passed through just like any other common members.
You can try to cast a SuperStruct to a subtype (throws on
failure).
If members have a common signature but uncommon return types, the
member _is_ forwarded and the return type is a SuperStruct of the
possible return types (this means it has any behavior common to
the return types). Thanks to Timon Gehr for the suggestion!
(http://forum.dlang.org/thread/jiucsrcvkfdzwinqp...@forum.dlang.org?page=2#post-n09600:241gel:241:40digitalmars.com)
A SuperStruct can now satisfy a range interface (this required
using mixed-in members instead of opDispatch).
Create a SuperStruct on the fly with pick or pickAmong (similar
to std.range's choose/chooseAmong, but works for any types, not
just ranges).
Example:
unittest {
import std.range, std.algorithm, std.container;
alias Container(T) = SuperStruct!(SList!T, Array!T);
Container!int slist = SList!int();
// We can call any members that are common among containers
slist.insert([1,2,3,4]);
assert(slist.front == 1);
// opSlice is supported on all the subtypes, but each returns a
different type
// Container.opSlice will return a SuperStruct of these types
auto slice = slist[]; // [1,2,3,4]
assert(slice.front == 1);
slice.popFront(); // [2,3,4]
assert(slice.front == 2);
// as slice is a SuperStruct of range types, it still works as
a range
slist.insert(slice); // [2,3,4] ~ [1,2,3,4]
assert(slist[].equal([2,3,4,1,2,3,4]));
}
