Re: The New DIP Process

2024-02-28 Thread Jonathan M Davis via Digitalmars-d-announce
On Wednesday, February 28, 2024 10:44:08 PM MST Brad Roberts via Digitalmars- d-announce wrote: > On 2/28/2024 7:34 PM, Jonathan M Davis via Digitalmars-d-announce wrote: > > On Wednesday, February 28, 2024 7:18:29 PM MST Mike Parker via > > Digitalmars-d-> > > announce

Re: The New DIP Process

2024-02-28 Thread Jonathan M Davis via Digitalmars-d-announce
On Wednesday, February 28, 2024 7:18:29 PM MST Mike Parker via Digitalmars-d- announce wrote: > On Wednesday, 28 February 2024 at 19:24:32 UTC, Jonathan M Davis > > wrote: > > I see that they're up on the NNTP server, and the web forum is > > hooked up to them, but the

Re: The New DIP Process

2024-02-28 Thread Jonathan M Davis via Digitalmars-d-announce
are these lists not going to have mailing lists like the others? - Jonathan M Davis

Re: Preparing for the New DIP Process

2024-01-25 Thread Jonathan M Davis via Digitalmars-d-announce
On Thursday, January 25, 2024 8:03:41 AM MST Max Samukha via Digitalmars-d- announce wrote: > On Monday, 22 January 2024 at 23:28:40 UTC, Jonathan M Davis > > wrote: > > Of course, ultimately, different programmers have different > > preferences, and none of us are go

Re: Would this be a useful construct to add to D? auto for constructor call.

2024-01-23 Thread Jonathan M Davis via Digitalmars-d-announce
On Tuesday, January 23, 2024 4:11:00 AM MST ryuukk_ via Digitalmars-d-announce wrote: > On Tuesday, 23 January 2024 at 06:30:08 UTC, Jonathan M Davis > > wrote: > > That being said, I expect that it would be pretty easy to write > > a mixin to do something like that

Re: Would this be a useful construct to add to D? auto for constructor call.

2024-01-22 Thread Jonathan M Davis via Digitalmars-d-announce
n to do something like that if you really wanted to. Also, if you're simply looking to not have to name the type, you could do dataGrid = new typeof(datagrid)(15); - Jonathan M Davis

Re: Preparing for the New DIP Process

2024-01-22 Thread Jonathan M Davis via Digitalmars-d-announce
e happy about everything in any language. So, of course, there are going to be some folks who are unhappy with how D defines private, but it's not a feature that has actually been causing us problems, and it really doesn't make sense at this point to change how it works. - Jonathan M Davis

Re: DLF September 2023 Planning Update

2023-11-15 Thread Jonathan M Davis via Digitalmars-d-announce
On Wednesday, November 15, 2023 3:26:27 AM MST Sergey via Digitalmars-d- announce wrote: > On Wednesday, 15 November 2023 at 09:27:53 UTC, Jonathan M Davis > > wrote: > > On Tuesday, November 14, 2023 12:37:29 PM MST Sergey via > > > > Digitalmars-d- announce wrote: &

Re: DLF September 2023 Planning Update

2023-11-15 Thread Jonathan M Davis via Digitalmars-d-announce
take care of it rather than require that new code slap editions stuff everywhere), but there is a good reason for the approach that they're currently looking at taking. - Jonathan M Davis

Re: DConf '23 Talk Videos

2023-09-20 Thread Jonathan M Davis via Digitalmars-d-announce
> definitive answer tomorrow. If I'm lucky, a full internal > cleaning of the graphics card and some new thermal paste will > solve it. I'm usually not that lucky, though :-) Clearly, your computer is just sick of hearing about dconf and decided to go on strike. ;) - Jonathan M Davis

Re: DIP 1028 "Make @safe the Default" is dead

2020-05-29 Thread Jonathan M Davis via Digitalmars-d-announce
se as necessary. For modules with C declarations, do as you think > best. > > For everyone else, carry on as before. Thank you. - Jonathan M Davis

Re: DIP 1028 "Make @safe the Default" is dead

2020-05-29 Thread Jonathan M Davis via Digitalmars-d-announce
at treating declarations differently from definitions would mean adding an exception to the rules and that such an exception would be very negative. - Jonathan M Davis

Re: Rationale for accepting DIP 1028 as is

2020-05-28 Thread Jonathan M Davis via Digitalmars-d-announce
On Thursday, May 28, 2020 2:50:44 AM MDT Daniel Kozak via Digitalmars-d- announce wrote: > On Thu, May 28, 2020 at 4:56 AM Jonathan M Davis via > > Digitalmars-d-announce wrote: > > As far as I can tell, Walter understands the issues but fundamentally > > disagrees with pret

Re: Rationale for accepting DIP 1028 as is

2020-05-27 Thread Jonathan M Davis via Digitalmars-d-announce
hecked by the compiler, whereas most everyone else thinks that weakening @safe is unacceptable. But since Walter managed to convince Atila, the DIP has been accepted. - Jonathan M Davis

Re: Rationale for accepting DIP 1028 as is

2020-05-27 Thread Jonathan M Davis via Digitalmars-d-announce
o think that it's ultimately a big deal. - Jonathan M Davis

Re: DIP1028 - Rationale for accepting as is

2020-05-27 Thread Jonathan M Davis via Digitalmars-d-announce
On Wednesday, May 27, 2020 8:13:52 PM MDT Bruce Carneal via Digitalmars-d- announce wrote: > On Thursday, 28 May 2020 at 01:14:43 UTC, Jonathan M Davis wrote: > > On Friday, May 22, 2020 12:09:16 PM MDT rikki cattermole via > > > > Digitalmars-d- announce wrote: >

Re: DIP1028 - Rationale for accepting as is

2020-05-27 Thread Jonathan M Davis via Digitalmars-d-announce
ow which access-level modifier applies - especially when looking at diffs in PRs. I would _love_ to see it become illegal to mass-apply @trusted (or even attributes in general), but I have no clue how easy it would be to get such a DIP accepted or how much screaming there would be over it if it were actually accepted. - Jonathan M Davis

Re: DIP1028 - Rationale for accepting as is

2020-05-27 Thread Jonathan M Davis via Digitalmars-d-announce
ode, but you must look for non-extern(D) declarations which have been implictly treated as @trusted by the compiler. @safe still has value (and may even provide more value in that it will be used more often), but it provides much weaker guarantees in the process. - Jonathan M Davis

Re: DIP1028 - Rationale for accepting as is

2020-05-27 Thread Jonathan M Davis via Digitalmars-d-announce
attribute on the function declaration actually meaning anything about whether the body was verified by the compiler. - Jonathan M Davis

Re: Release D 2.089.0

2019-11-11 Thread Jonathan M Davis via Digitalmars-d-announce
minds me of someone complaining that they couldn't just unzip the dmd install on top of another and have it work (their code no longer compiled aftery they'd just unzipped a release of dmd/phobos which had a split std.datetime on top of one that didn't). - Jonathan M Davis

Re: DIP 1021--Argument Ownership and Function Calls--Formal Assessment

2019-10-22 Thread Jonathan M Davis via Digitalmars-d-announce
so someone has to then convince him otherwise for it to not be accepted. Fortunately, while Walter certainly doesn't have a perfect track record, he has a pretty darn good one, or D wouldn't be what it is today. - Jonathan M Davis

Re: Release Candidate [was: Re: Beta 2.087.0]

2019-07-04 Thread Jonathan M Davis via Digitalmars-d-announce
orted using it IIRC). I don't know what the current state of that is, but I recall there being a deprecation message about that behavior going away. So, if that behavior finally went away, then code could have compiled with the previous release but not the new one. - Jonathan M Davis

Re: Release D 2.087.0

2019-07-04 Thread Jonathan M Davis via Digitalmars-d-announce
itself), it risks breaking any time that the build system is altered. - Jonathan M Davis

Re: DIP 1013--The Deprecation Process--Formal Assessment

2019-06-12 Thread Jonathan M Davis via Digitalmars-d-announce
master/DIPs/accepted/DIP1013.md > > So what is the "version" in @@@DEPRECATED_[version]@@@ supposed > to be? That still seems to be ambiguous. How is it ambiguous? It says right in the same sentence that @@@DEPRECATED_[version]@@@ is mentioned. - Jonathan M Davis

Re: Phobos is now compiled with -preview=dip1000

2019-05-17 Thread Jonathan M Davis via Digitalmars-d-announce
eneral, it's just going to be more annoying than it's worth. Time will tell though. - Jonathan M Davis

Re: Phobos is now compiled with -preview=dip1000

2019-05-17 Thread Jonathan M Davis via Digitalmars-d-announce
nathan M Davis

Re: bool (was DConf 2019 AGM Livestream)

2019-05-15 Thread Jonathan M Davis via Digitalmars-d-announce
pressing problems. The small stuff does matter, and it's easier to tackle, but if we're consistently trying to solve the small problems without tackling the larger ones, then we have a serious problem. - Jonathan M Davis

Re: Static Webpages of Forum Threads

2019-05-13 Thread Jonathan M Davis via Digitalmars-d-announce
it enough. ;) - Jonathan M Davis

Re: bool (was DConf 2019 AGM Livestream)

2019-05-13 Thread Jonathan M Davis via Digitalmars-d-announce
one can come up with a way to convince Walter to view bools differently (which I very much doubt is going to happen), I think that it's quite clear that we're just going to have to learn to continue to live with the status quo on this issue. - Jonathan M Davis

Re: bool (was DConf 2019 AGM Livestream)

2019-05-12 Thread Jonathan M Davis via Digitalmars-d-announce
ler than almost all of the issues that we have to worry about and consider having DIPs for. Personally, I'm not at all happy that this DIP was rejected, but I think that continued debate on it is a waste of everyone's time. - Jonathan M Davis

Re: DIP 1018--The Copy Constructor--Formal Review

2019-02-25 Thread Jonathan M Davis via Digitalmars-d-announce
_ of discussion and was revised accordingly. So, while Walter and Andrei may have considered it a priority, it still took a while for it to get to the point that it was acceptable. - Jonathan M Davis

Re: Blog post: What D got wrong

2018-12-18 Thread Jonathan M Davis via Digitalmars-d-announce
nly realized it when I read Bartosz's article on the subject). I just understood how to use them and didn't think about it, though once I did realize it, I felt stupid for not having realized it. - Jonathan M Davis

Re: Blog post: What D got wrong

2018-12-18 Thread Jonathan M Davis via Digitalmars-d-announce
s a high risk of marking a function as @trusted later when someone adds it and doesn't realize that @trusted was applied. - Jonathan M Davis

Re: Blog post: What D got wrong

2018-12-18 Thread Jonathan M Davis via Digitalmars-d-announce
On Tuesday, December 18, 2018 7:02:43 PM MST H. S. Teoh via Digitalmars-d- announce wrote: > On Tue, Dec 18, 2018 at 06:53:02PM -0700, Jonathan M Davis via > Digitalmars-d-announce wrote: [...] > > > I confess that I do tend to think about things from the standpoint of > &g

Re: Blog post: What D got wrong

2018-12-18 Thread Jonathan M Davis via Digitalmars-d-announce
On Tuesday, December 18, 2018 6:35:34 AM MST Pjotr Prins via Digitalmars-d- announce wrote: > On Tuesday, 18 December 2018 at 11:25:17 UTC, Jonathan M Davis > > wrote: > > Of course, even if we _did_ have a solution for reversing > > attributes, slapping an attribute on

Re: Blog post: What D got wrong

2018-12-18 Thread Jonathan M Davis via Digitalmars-d-announce
attributes are mass-applied). So, there is no silver bullet here (though regardless of whether mass-applying attributes is something that should ever be considered good practice, we really should add a way to be able to reverse them). - Jonathan M Davis

Re: Blog post: What D got wrong

2018-12-12 Thread Jonathan M Davis via Digitalmars-d-announce
ghs the loss, but that doesn't mean that the problem isn't there, just that many folks don't care and think that the tradeoff is worth it. - Jonathan M Davis

Re: A brief survey of build tools, focused on D

2018-12-12 Thread Jonathan M Davis via Digitalmars-d-announce
r more than pulling in dependencies. Beyond that, I suspect that if we really wanted to make dub truly flexible, we'd have to look into making it more plugin-based to allow alternate build systems, but that's a _much_ larger shift in how it works. Regardless, it would require manpower that isn't currently being targeted at dub. - Jonathan M Davis

Re: Blog post: What D got wrong

2018-12-12 Thread Jonathan M Davis via Digitalmars-d-announce
(though if the default were changed to const or immutable, we'd probably see the range API be changed to use the classic, functional head/tail list mechanism rather than front and popFront, which could very well be an improvement anyway). - Jonathan M Davis

Re: DIP 1015--Deprecation of Implicit Conversion of Int. & Char. Literals to bool--Formal Assement

2018-11-13 Thread Jonathan M Davis via Digitalmars-d-announce
On Tuesday, November 13, 2018 9:27:29 PM MST Nicholas Wilson via Digitalmars-d-announce wrote: > On Wednesday, 14 November 2018 at 04:24:20 UTC, Jonathan M Davis > > wrote: > > Given how strong the negative response is to this and how > > incomprenhensible a number of us find

Re: DIP 1015--Deprecation of Implicit Conversion of Int. & Char. Literals to bool--Formal Assement

2018-11-13 Thread Jonathan M Davis via Digitalmars-d-announce
ents are solid without getting anything into the mix that could come across as insulting. - Jonathan M Davis

Re: DIP 1015--Deprecation of Implicit Conversion of Int. & Char. Literals to bool--Formal Assement

2018-11-12 Thread Jonathan M Davis via Digitalmars-d-announce
IP was convincing enough, and its failure is certainly disappointing. - Jonathan M Davis

Re: DIP 1014--Hooking D's struct move semantics--Has Been Accepted

2018-11-07 Thread Jonathan M Davis via Digitalmars-d-announce
tarts getting used frequently, there's definitely a problem, but there are use cases, where it's going to be invaluable. - Jonathan M Davis

Re: Copy Constructor DIP and implementation

2018-10-11 Thread Jonathan M Davis via Digitalmars-d-announce
s exactly the same problem. It should always be possible to make code compile with both master and the latest release without deprecation messages, since otherwise, even programmers who are completely on top of things could end up having to deal with a flood of deprecation messages that they can't fix. - Jonathan M Davis

Re: Copy Constructor DIP and implementation

2018-09-25 Thread Jonathan M Davis via Digitalmars-d-announce
ing to be a > DIP on its own. Yay! Thank you. - Jonathan M Davis

Re: Copy Constructor DIP and implementation

2018-09-24 Thread Jonathan M Davis via Digitalmars-d-announce
On Monday, September 24, 2018 9:33:19 PM MDT Manu via Digitalmars-d-announce wrote: > On Mon, 24 Sep 2018 at 16:22, Jonathan M Davis via > > Digitalmars-d-announce wrote: > > On Monday, September 24, 2018 3:20:28 PM MDT Manu via > > Digitalmars-d-announce> > >

Re: Copy Constructor DIP and implementation

2018-09-24 Thread Jonathan M Davis via Digitalmars-d-announce
On Monday, September 24, 2018 7:59:36 PM MDT Nicholas Wilson via Digitalmars-d-announce wrote: > On Monday, 24 September 2018 at 23:22:13 UTC, Jonathan M Davis > > wrote: > > @implicit on copy constructors is outright bad. It would just > > be a source of bugs. Every time

Re: Copy Constructor DIP and implementation

2018-09-24 Thread Jonathan M Davis via Digitalmars-d-announce
en it's clearly going to be a source of bugs if it's required to be on copy constructors. And it just needlessly adds to the attribute soup. At least if it were added for regular constructors, it would be adding value. For copy constructors, it's just adding annoyance and the risk of bugs. - Jonathan M Davis

Re: Copy Constructor DIP and implementation

2018-09-24 Thread Jonathan M Davis via Digitalmars-d-announce
On Monday, September 24, 2018 10:44:01 AM MDT Meta via Digitalmars-d- announce wrote: > On Sunday, 23 September 2018 at 01:08:50 UTC, Jonathan M Davis > > wrote: > > @implicit is just there because of the fear of breaking a > > theoretical piece of code that's going

Re: Copy Constructor DIP and implementation

2018-09-22 Thread Jonathan M Davis via Digitalmars-d-announce
On Saturday, September 22, 2018 8:40:15 PM MDT Nicholas Wilson via Digitalmars-d-announce wrote: > On Sunday, 23 September 2018 at 01:08:50 UTC, Jonathan M Davis > > wrote: > > On Saturday, September 22, 2018 6:13:25 PM MDT Adam D. Ruppe > > > > via D

Re: Copy Constructor DIP and implementation

2018-09-22 Thread Jonathan M Davis via Digitalmars-d-announce
es would continue to work just fine even if it did exist. - Jonathan M Davis

Re: Copy Constructor DIP and implementation

2018-09-18 Thread Jonathan M Davis via Digitalmars-d-announce
itch? Why force everyone to mark their copy constructors with @implicit forever? The whole point of adding the attribute was to avoid breaking existing code. - Jonathan M Davis

Re: Copy Constructor DIP and implementation

2018-09-17 Thread Jonathan M Davis via Digitalmars-d-announce
r accepted. So, while I understand that you want implicit construction, I think that it's a huge mistake to tie that up into copy constructors, particularly since it really doesn't make sense to have copy constructors that aren't implicit, and having @implicit for copy constructiors is going to cause bugs when it's forgotten. - Jonathan M Davis

Re: Copy Constructor DIP and implementation

2018-09-17 Thread Jonathan M Davis via Digitalmars-d-announce
On Monday, September 17, 2018 5:14:28 PM MDT tide via Digitalmars-d-announce wrote: > On Monday, 17 September 2018 at 19:10:27 UTC, Jonathan M Davis > > wrote: > > Basically, @implicit is being proposed out of fear that > > someone, somewhere wrote a constructor that had wha

Re: Copy Constructor DIP and implementation

2018-09-17 Thread Jonathan M Davis via Digitalmars-d-announce
structors with. We should just have a -dip* flag as a transition to deal with the theoretical breakage that @implicit is supposed to prevent (as well as gives us a chance to kick the tires of the implementation a bit first) and not do anything special to mark copy constructors aside from what their parameters are. - Jonathan M Davis

Re: Copy Constructor DIP and implementation

2018-09-17 Thread Jonathan M Davis via Digitalmars-d-announce
uggy code. This is clearly a case of making the language worse long term in order to avoid a theoretical problem in the short term. - Jonathan M Davis

Re: Copy Constructor DIP and implementation

2018-09-17 Thread Jonathan M Davis via Digitalmars-d-announce
On Monday, September 17, 2018 7:30:24 AM MDT rmc via Digitalmars-d-announce wrote: > On Wednesday, 12 September 2018 at 16:40:45 UTC, Jonathan M Davis > > wrote: > > [snip] > > Personally, I'd rather that we just risk the code breakage > > caused by not having an attr

Re: Copy Constructor DIP and implementation

2018-09-12 Thread Jonathan M Davis via Digitalmars-d-announce
On Wednesday, September 12, 2018 5:55:05 PM MDT Nicholas Wilson via Digitalmars-d-announce wrote: > On Wednesday, 12 September 2018 at 23:36:11 UTC, Jonathan M Davis > > wrote: > > On Wednesday, September 12, 2018 5:17:44 PM MDT Nicholas Wilson > > > > via D

Re: Copy Constructor DIP and implementation

2018-09-12 Thread Jonathan M Davis via Digitalmars-d-announce
t later anyway), but either way, saying that @implicit has anything to do with adding implicit construction to D like C++ has is currently false. In fact, the DIP specifically makes it an error to use @implicit on anything other than a copy constructor. - Jonathan M Davis

Re: Copy Constructor DIP and implementation

2018-09-12 Thread Jonathan M Davis via Digitalmars-d-announce
ision, I wouldn't introduce @implicit and would risk the code breakage (which I would expect to be pretty much non-existent much as it theoretically could happen), but it's not my decision. - Jonathan M Davis

Re: Copy Constructor DIP and implementation

2018-09-12 Thread Jonathan M Davis via Digitalmars-d-announce
On Wednesday, September 12, 2018 1:18:11 PM MDT Gary Willoughby via Digitalmars-d-announce wrote: > On Wednesday, 12 September 2018 at 16:40:45 UTC, Jonathan M Davis > > wrote: > > Ultimately, I expect that if we add any attribute for this, > > people coming to D are goi

Re: Copy Constructor DIP and implementation

2018-09-12 Thread Jonathan M Davis via Digitalmars-d-announce
opy, this would clearly forever be something that we added just because we has postblit constructors first, whereas @implicit at least _might_ be used for something more. It would still feel weird and hacky if it never was used for anything more, but at least we'd be future-proofing the language a bit, and @implicit does make _some_ sense after it's explained, even if very few people (if any) will initially think that it makes sense. - Jonathan M Davis

Re: DIP Draft Reviews

2018-09-06 Thread Jonathan M Davis via Digitalmars-d-announce
nd Andrei to need to put big changes through the DIP process just like the rest of us do, but given that they're the only ones deciding what's accepted, it makes the whole thing rather weird when a DIP comes from them. - Jonathan M Davis

Re: Beta 2.082.0

2018-08-18 Thread Jonathan M Davis via Digitalmars-d-announce
1ff8760450fcab/detection > > > > Windows Defender also reports it as clean. > > Good to hear that paying the certificate ransom helped making > peace with the blackmailers ;). Technically, I think that they're extortionists rather than blackmailers. ;) - Jonathan M Davis

dxml 0.4.0 released

2018-08-04 Thread Jonathan M Davis via Digitalmars-d-announce
://github.com/jmdavis/dxml/tree/v0.4.0 Dub: http://code.dlang.org/packages/dxml For those who haven't seen it, here's a link to my dconf talk on dxml: http://dconf.org/2018/talks/davis.html - Jonathan M Davis

Re: The dub documentation is now on dub.pm

2018-07-19 Thread Jonathan M Davis via Digitalmars-d-announce
sdl came later. However, there was a lot of push back when Sonke made sdl the default, so json not only didn't get phased out, but it became the default again. - Jonathan M Davis

Re: I have a plan.. I really DO

2018-07-01 Thread Jonathan M Davis via Digitalmars-d-announce
mistake they did, and they don't even know they make a > mistake, silly them... ;) What should and shouldn't go in the standard library for a language is something that's up for a lot of debate and is likely to often be a point of contention. There is no clear right or wrong here. Languages that have had very sparse standard libraries have done quite well, and languages that have had kitchen sink libraries have done quite well. There are pros and cons to both approaches. - Jonathan M Davis

Re: Encouraging preliminary results implementing memcpy in D

2018-06-14 Thread Jonathan M Davis via Digitalmars-d-announce
some companies are better about it than others. - Jonathan M Davis

Re: Encouraging preliminary results implementing memcpy in D

2018-06-14 Thread Jonathan M Davis via Digitalmars-d-announce
se, what he has implemented is pretty much what's in Phobos except for the fact that he set up his to take arguments, whereas Phobos' solution just takes the function(s) to call, so anything that it does has to be self-contained. - Jonathan M Davis

Re: SecureD moving to GitLab

2018-06-09 Thread Jonathan M Davis via Digitalmars-d-announce
hen employers try to claim anything unrelated to your job that you do in your free time. _That_ is completely inappropriate, but some employers try anyway, and depending on which state you live in and what you signed for the company, they may or may not be able to come after you even if it's ridiculous for them to be able to. - Jonathan M Davis

Re: GitHub could be acquired by Microsoft

2018-06-07 Thread Jonathan M Davis via Digitalmars-d-announce
o be somewhere like github or gitlab or bitbucket or whatever is another matter entirely, but ultimately, I think that the main benefits of DVCS is that it removes the dependency on the central repo from any operations that don't actually need the central repo, not that it removes the need for a central repo, because it really doesn't - not if you want to be organized about releases anyway. - Jonathan M Davis

Re: SecureD moving to GitLab

2018-06-05 Thread Jonathan M Davis via Digitalmars-d-announce
On Tuesday, June 05, 2018 19:15:12 biocyberman via Digitalmars-d-announce wrote: > On Tuesday, 5 June 2018 at 11:09:31 UTC, Jonathan M Davis wrote: > > [...] > > Very informative. I don't live in the US, but this gives me a > feeling of how tough life can be over there fo

Re: SecureD moving to GitLab

2018-06-05 Thread Jonathan M Davis via Digitalmars-d-announce
might try and do anything to you with the legal system - and of course, you don't want to be in a position where your employer fires you. So, an abundance of caution is sometimes warranted even if it arguably shouldn't need to be. - Jonathan M Davis

Re: GitHub could be acquired by Microsoft

2018-06-04 Thread Jonathan M Davis via Digitalmars-d-announce
ting you turn it off). It's certainly not desriable that they bought github, but it probably won't have any obvious effects for a while. The biggest concerns probably have to do with collecting data on users, and github was doutblessly doing that already. - Jonathan M Davis

Re: GitHub could be acquired by Microsoft

2018-06-03 Thread Jonathan M Davis via Digitalmars-d-announce
maybe this will encourage online repo hosting to become less of a monopoly as folks move elsewhere due to their concerns about Microsoft. - Jonathan M Davis

Re: serialport v1.0.0

2018-05-13 Thread Jonathan M Davis via Digitalmars-d-announce
g like functionality for talking to serial ports. And what would having it be in Phobos buy you over just grabbing it from code.dlang.org? - Jonathan M Davis

Re: iopipe v0.0.4 - RingBuffers!

2018-05-11 Thread Jonathan M Davis via Digitalmars-d-announce
b it than to make what they had faster, but I don't know. Either way, it sounds like Mac OS X either didn't take their grep from FreeBSD in this case, or they took it from an older version before FreeBSD switching to using GNU's grep. - Jonathan M Davis

Re: dxml 0.3.0 released

2018-04-20 Thread Jonathan M Davis via Digitalmars-d-announce
On Friday, April 20, 2018 16:07:06 Jesse Phillips via Digitalmars-d-announce wrote: > On Friday, 20 April 2018 at 00:46:38 UTC, Jonathan M Davis wrote: > > Yes. I would have thought that that was clear. It throws if any > > of the characters or sequence of characters in the argu

Re: dxml 0.3.0 released

2018-04-20 Thread Jonathan M Davis via Digitalmars-d-announce
On Friday, April 20, 2018 08:45:45 Dejan Lekic via Digitalmars-d-announce wrote: > On Thursday, 19 April 2018 at 14:40:58 UTC, Jonathan M Davis > > wrote: > > Well, since I'm going to be talking about dxml at dconf, and > > it's likely that I'll be talking about stuff that w

Re: dxml 0.3.0 released

2018-04-19 Thread Jonathan M Davis via Digitalmars-d-announce
On Thursday, April 19, 2018 23:00:03 Jesse Phillips via Digitalmars-d- announce wrote: > On Thursday, 19 April 2018 at 14:40:58 UTC, Jonathan M Davis > > wrote: > > I won't repeat everything that's in the changelog, but the > > biggest changes are that writer suppo

Re: dxml 0.3.0 released

2018-04-19 Thread Jonathan M Davis via Digitalmars-d-announce
t busy with school again and never got back to it), and it shows no sign of ever being completed. - Jonathan M Davis

dxml 0.3.0 released

2018-04-19 Thread Jonathan M Davis via Digitalmars-d-announce
://jmdavisprog.com/docs/dxml/0.3.0/ Github: https://github.com/jmdavis/dxml/tree/v0.3.0 Dub: http://code.dlang.org/packages/dxml - Jonathan M Davis

Re: DIP 1009 (Add Expression-Based Contract Syntax) Accepted

2018-04-11 Thread Jonathan M Davis via Digitalmars-d-announce
On Wednesday, April 11, 2018 07:47:14 H. S. Teoh via Digitalmars-d-announce wrote: > On Tue, Apr 10, 2018 at 11:43:00PM -0600, Jonathan M Davis via > Digitalmars-d-announce wrote: [...] > > > IMHO, for contracts to be worth much outside of the inheritance case, > > we'd need

Re: #include C headers in D code

2018-04-11 Thread Jonathan M Davis via Digitalmars-d-announce
ng tied to ldc is okay. It's quite another to tell someone who isn't familiar with D that in order to use D, they have to use a feature which only works with a specific compiler that is not the reference compiler and which will likely never work with the reference compiler. - Jonathan M Davis

Re: DIP 1009 (Add Expression-Based Contract Syntax) Accepted

2018-04-10 Thread Jonathan M Davis via Digitalmars-d-announce
contracts are compiled in based on whether the caller used -release or not rather than whether the callee did. If that were done, then there would be real value in using contracts, and I'd be a lot more excited about the new syntax. As it is, it seems like a nice improvement that's ultimately pointless. - Jonathan M Davis

Re: DIP 1009 (Add Expression-Based Contract Syntax) Accepted

2018-04-06 Thread Jonathan M Davis via Digitalmars-d-announce
d so that contracts were compiled in based on how the caller were compiled rather than the callee - then maybe having an actual contract would make sense, but as it stands, I don't see the point. - Jonathan M Davis

Re: Why think unit tests should be in their own source code hierarchy instead of side-by-side

2018-03-23 Thread Jonathan M Davis via Digitalmars-d-announce
On Saturday, March 24, 2018 00:51:07 Tony via Digitalmars-d-announce wrote: > On Saturday, 24 March 2018 at 00:12:23 UTC, Jonathan M Davis > > wrote: > > On Friday, March 23, 2018 22:42:34 Tony via > > > > Digitalmars-d-announce wrote: > >> On Friday, 23 Ma

Re: Why think unit tests should be in their own source code hierarchy instead of side-by-side

2018-03-23 Thread Jonathan M Davis via Digitalmars-d-announce
are > adding or changing. Insisting on writing the tests before writing the code doesn't help with the kind of situation that H. S. Teoh is describing. And arguably it exacerbates the problem. Regardless, it doesn't help when the code has already been written. - Jonathan M Davis

Re: Why think unit tests should be in their own source code hierarchy instead of side-by-side

2018-03-23 Thread Jonathan M Davis via Digitalmars-d-announce
tests right after the functions. And that doesn't even involve a separate file. Obviously, YMMV, but in my experience, having the tests _immediately_ after what they're testing is vastly more maintainable than having the tests elsewhere. - Jonathan M Davis

Re: Why think unit tests should be in their own source code hierarchy instead of side-by-side

2018-03-22 Thread Jonathan M Davis via Digitalmars-d-announce
uot;], "versions": ["dxmlTests"] } } And then I have scripts such as test.sh === #!/bin/sh dub test --build=doTests === to run the tests. I had to actively work around dub and what it does with unit tests in order to not have all of dxml's tests compiled into any project which had dxml as a dependency. - Jonathan M Davis

Re: Why think unit tests should be in their own source code hierarchy instead of side-by-side

2018-03-22 Thread Jonathan M Davis via Digitalmars-d-announce
e unit tests of all of your dependencies regardless of what dmd does, but even if dub were not doing that, we'd still have a problem with the language itself. - Jonathan M Davis

Re: User Stories: Funkwerk

2018-03-17 Thread Jonathan M Davis via Digitalmars-d-announce
On Saturday, March 17, 2018 20:12:08 bauss via Digitalmars-d-announce wrote: > On Saturday, 17 March 2018 at 19:54:07 UTC, Jonathan M Davis > > wrote: > > On Saturday, March 17, 2018 12:48:07 bauss via > > > > Digitalmars-d-announce wrote: > >> On Friday, 16 Ma

Re: User Stories: Funkwerk

2018-03-17 Thread Jonathan M Davis via Digitalmars-d-announce
++ syntax > > Also "auto" can be omitted. > > foreach (element; elements) Not only can be. It must be. auto is not legal in a foreach loop in D, which is arguably a bit inconsistent, but for better or worse, that's the way it is. - Jonathan M Davis

Re: Vision document for H1 2018

2018-03-16 Thread Jonathan M Davis via Digitalmars-d-announce
fit even if you never do anything for dmd, druntime, or Phobos. In some ways, that's probably our biggest need. But regardless, if you're interested in helping out the D ecosystem, there are plenty of options. - Jonathan M Davis

Re: The D Language Foundation at Open Collective

2018-03-13 Thread Jonathan M Davis via Digitalmars-d-announce
gt; > https://www.reddit.com/r/d_language/comments/83vbz6/the_d_foundation_at_ > > open_collective/ > The Website needs the link, too!: > https://dlang.org/foundation/donate.html BTW, opencollective.com has a link to windfair.net listed in your backer profile, but it links via https, an

Re: Vision document for H1 2018

2018-03-11 Thread Jonathan M Davis via Digitalmars-d-announce
least to begin with. D does things differently, so anyone learning it is just going to have to expect to deal with a learning curve. How steep a curve that is is going to depend on the programmer's experience and background, but it's going to be there regardless. - Jonathan M Davis

Re: Vision document for H1 2018

2018-03-11 Thread Jonathan M Davis via Digitalmars-d-announce
my phone). When dealing with building on Windows, it would definitely pay to read the instructions and not assume anything about make, since unfortunately, the Windows build uses the digital mars make, which is severely limited in comparison to the BSD make or GNU make. - Jonathan M Davis

Re: Article: Why Const Sucks

2018-03-06 Thread Jonathan M Davis via Digitalmars-d-announce
On Tuesday, March 06, 2018 19:06:25 Martin Nowak via Digitalmars-d-announce wrote: > On Tuesday, 6 March 2018 at 18:17:58 UTC, Jonathan M Davis wrote: > > I'm not actually convinced that killing auto-decoding is really > > much better. > > I don't think the problem is au

Re: Article: Why Const Sucks

2018-03-06 Thread Jonathan M Davis via Digitalmars-d-announce
On Tuesday, March 06, 2018 10:47:36 H. S. Teoh via Digitalmars-d-announce wrote: > On Tue, Mar 06, 2018 at 01:31:39PM -0500, Steven Schveighoffer via Digitalmars-d-announce wrote: > > On 3/6/18 10:39 AM, Jonathan M Davis wrote: > > > Yeah. If you're dealing with generi

Re: Article: Why Const Sucks

2018-03-06 Thread Jonathan M Davis via Digitalmars-d-announce
hen we do new stuff or redesign old stuff. Frequently, the end result is better, but it's rarely perfect. - Jonathan M Davis

  1   2   3   4   5   6   >