I want to suggest some things (for the switch and the foreach loop) and I was wondering, just the developers take suggestions? And if yes, did the made anything that someone else suggested?

On 8/17/20 12:50 PM, Flade wrote:
> I want to suggest some things (for the switch and the foreach loop) and I was wondering, just the developers take suggestions? And if yes, did the made anything that someone else suggested?

It never hurts to ask here. Though if you are new to D, you mean find that your suggestions are already covered. What are your suggestions?

-Steve

On Monday, 17 August 2020 at 16:50:52 UTC, Flade wrote:
> I want to suggest some things (for the switch and the foreach loop) and I was wondering, just the developers take suggestions? And if yes, did the made anything that someone else suggested?

The official, formal way to suggest a language change is to write a D Improvement Proposal, or "DIP" [1]: a document that describes the proposed change along with the rationale behind it. Every major change to the D language has to go through this process, even changes made by Walter Bright, the creator of D.

Writing a DIP is a lot of work, though, so it's a good idea to discuss your suggestions with other members of the D community on the forums first. There are a lot of smart people here with ideas for how D could be improved, so you're very likely to get useful feedback.

[1] https://github.com/dlang/DIPs/

On Monday, 17 August 2020 at 17:00:54 UTC, Steven Schveighoffer wrote:
> On 8/17/20 12:50 PM, Flade wrote:
>> I want to suggest some things (for the switch and the foreach loop) and I was wondering, just the developers take suggestions? And if yes, did the made anything that someone else suggested?
>
> It never hurts to ask here. Though if you are new to D, you mean find that your suggestions are already covered. What are your suggestions?
>
> -Steve

Thanks a lot for the quick answer! Maybe my suggestions are covered (yes I'm actually new to D) but thanks a lot for listening! I will actually talk for the switch statement now.

First and most importantly I would say to automatically break in each case because from my personal experience, this is what we do all the time. Also D let's you cover ranges so if you want for example to switch in (x) and cover cases 1 through 5, you would do "case 1: .. case 5:" so in D specifically there is no reason to not break automatically. Also there is the "goto" statement to be used with switch statements so even if someone needs to check another case in a rare scenario, we are covered! If there is something I don't know or I don't understand here please forgive me and correct me!

Second, there is a small detail. You see I think that when covering ranges, we should change the syntax a little bit.

Current is
case 1: .. case 6:
It will be better to become
case 1 .. case 6:
Or even better
case 1 .. 6:

Of course this is just how it looks better to me but I also believe that it combines and fits better with the way we cover some specif cases which is done with: "case 1,3,4,7" and for me it makes sense that we don't repeat the word "case" multiple times.

So yeah that was me suggestions. I'm new to D and I'm in LOVE with the language!!! It just wanted to try to help with something even if it's just some small details and of course I want mind if this things won't be made. Thanks a lot for your time and effort sir!

On Monday, 17 August 2020 at 17:04:22 UTC, Paul Backus wrote:
> On Monday, 17 August 2020 at 16:50:52 UTC, Flade wrote:
>> I want to suggest some things (for the switch and the foreach loop) and I was wondering, just the developers take suggestions? And if yes, did the made anything that someone else suggested?
>
> The official, formal way to suggest a language change is to write a D Improvement Proposal, or "DIP" [1]: a document that describes the proposed change along with the rationale behind it. Every major change to the D language has to go through this process, even changes made by Walter Bright, the creator of D.
>
> Writing a DIP is a lot of work, though, so it's a good idea to discuss your suggestions with other members of the D community on the forums first. There are a lot of smart people here with ideas for how D could be improved, so you're very likely to get useful feedback.
>
> [1] https://github.com/dlang/DIPs/

Thanks a lot for the answer! I listed me suggestions here (see the comments) and as you can see, it's not something important (well the first thing is a little bit tbh) just some small details (tho as people say, details is what makes best) so I think I'll first take some opinions to see what other people say.

Hi there! Sorry, have to keep it short.

> First and most importantly I would say to automatically break in each case

Nothing new, folks already discussed this suggestion over ten years ago, when D2, the current language version, was still fresh. You can check it out here: https://forum.dlang.org/post/hdr46b$1770$1@digitalmars.com

In short: "either behave like C, or raise a compile-time error".

> Or even better
> case 1 .. 6:

This is covered in the FAQ: https://dlang.org/articles/faq.html#case_range

On Monday, 17 August 2020 at 21:50:18 UTC, oddp wrote:
> Hi there! Sorry, have to keep it short.
>
>> First and most importantly I would say to automatically break in each case
>
> Nothing new, folks already discussed this suggestion over ten years ago, when D2, the current language version, was still fresh. You can check it out here: https://forum.dlang.org/post/hdr46b$1770$1@digitalmars.com
>
> In short: "either behave like C, or raise a compile-time error".
>
>> Or even better
>> case 1 .. 6:
>
> This is covered in the FAQ: https://dlang.org/articles/faq.html#case_range

Oh! So I suppose the developers just don't agree and don't want to do this things?

On Monday, 17 August 2020 at 21:50:18 UTC, oddp wrote:
> Hi there! Sorry, have to keep it short.
>
>> First and most importantly I would say to automatically break in each case
>
> Nothing new, folks already discussed this suggestion over ten years ago, when D2, the current language version, was still fresh. You can check it out here: https://forum.dlang.org/post/hdr46b$1770$1@digitalmars.com
>
> In short: "either behave like C, or raise a compile-time error".
>
>> Or even better
>> case 1 .. 6:
>
> This is covered in the FAQ: https://dlang.org/articles/faq.html#case_range

Forget my previous comment! I understand anything now. Thanks a lot for your time!