Re: Phobos is now compiled with -preview=dip1000
On Saturday, 18 May 2019 at 19:44:37 UTC, Walter Bright wrote: If all access to internals is returned by ref, those lifetimes are restricted to the current expression. Oh my god, I try my best to be open-minded, but talking about dip1000 design with you is like pulling teeth *at best*. Yes, containers work perfectly if you allocate them on the stack and use their contents during the current stack frame, and then de-allocate them statically. By definition, this represents 0% of the use cases of dynamic containers. Dynamic containers need methods like "push_back", "reserve", "resize", "concatenate" or "clear", which are all impossible to implement with dip1000 without making their implementations trusted, which in turns opens up the program to use-after-free memory corruption. See also: https://forum.dlang.org/post/qbbipvkjqjeweasxk...@forum.dlang.org https://forum.dlang.org/post/rxmwjjphnmkszaxon...@forum.dlang.org Have you talked to Atila Neves at all for the past six months? Why the hell are we having this discussion? This is not a new issue. I have raised it repeatedly in the past (I can even dig up the posts if you're interested; I remember writing a fairly in-depth analysis at some point). Atila's automem and Skoppe's spasm have the same limitation: you can't reallocate memory without writing unsafe code (I'm told spasm gets around that by never deallocating anything). Honestly, the fact that you're the only person with a coherent vision of dip1000, and yet you keep ignoring problems when they're pointed out to you is both worrying and infuriating. Eg: So far, the only real shortcoming in the initial design was revealed by the put() semantics, and was fixed with that PR that transmitted scope-ness through the first argument. Like, yes, I understand that dip1000 is an achievement even if it doesn't allow for resizable containers, and that immutable already allow for functional programming patterns and that's great, but you need to stop acting like everything's going perfect when community members (including highly involved library writers) have complained about the same things over and over again (imprecise semantics, lack of documentation, the resize() use case) and you've kept ignoring them. Seriously, I'm not asking for much. I'm not demanding you take any architecture decision or redesign the language (like some people are prone to demanding here). But it would be nice if you stopped acting like you didn't read a word I wrote, over and over again.
Re: Phobos is now compiled with -preview=dip1000
If all access to internals is returned by ref, those lifetimes are restricted to the current expression.
Re: Phobos is now compiled with -preview=dip1000
On Friday, 17 May 2019 at 20:04:42 UTC, Walter Bright wrote: Dip1000 is key to enable containers to control access to pointers to their innards that they expose. I haven't looked at the subject for a while, but every time I did the takeaway was the same: dip1000 works great for containers until you need to reallocate or free something, at which point it's back to @trusted code with you. I think you said at some point "It's still useful, because it reduces the surface of code that needs to be checked", but even then saying containers can "control access to the data they expose" is a little optimistic. They only control that access as long as you don't need to call resize(). I'd wager that a large fraction of dangling pointer errors made by non-beginner C++ developpers come specifically from this use case.
Re: dlang.ru is updated
Unfortunately, now (and the last few years) dlang.ru is pretty useless.
Re: dlang.ru is updated
On Saturday, 18 May 2019 at 09:19:24 UTC, 9il wrote: On Saturday, 18 May 2019 at 06:26:10 UTC, Suliman wrote: On Saturday, 18 May 2019 at 03:01:33 UTC, 9il wrote: On Thursday, 16 May 2019 at 12:25:52 UTC, Suliman wrote: [...] Bullshit! I have checked the dlang.ru at RKN [1] registry and there are no dlang.ru in it. I checked with two providers from Russia and access works. Don't bug the forum with provocations or simply wait for DNS update. [1] - https://eais.rkn.gov.ru/ It was banned by IP. I checked it two weeks ago. It work very strange even from single mobile providers. https://imgur.com/a/NN3Apfo Well, yes this IP 37.252.127.244 is blocked for me and the checker [1] shows it belongs to dlang.ru (however the site itself works well). This was done by the court's decision [2] at 13.04.2018, more than a year ago. The information can be checked at [3]. You picked an already blocked IP. [1] https://ipinfo.info/html/ip_checker.php [2] https://www.mos-gorsud.ru/rs/taganskij/services/cases/civil/details/2cc72aea-39e7-4f8e-adc9-37d170966efa [3] http://blocklist.rkn.gov.ru/ Or, if you picked it a long time ago, then probably they blocked a Europe's subnet with this IP (because of telegram, games or drugs). However, nothing in this information says that they wanted to block dlang.ru. Placing the site at a new IP will solve the problem.
Re: dlang.ru is updated
On Saturday, 18 May 2019 at 06:26:10 UTC, Suliman wrote: On Saturday, 18 May 2019 at 03:01:33 UTC, 9il wrote: On Thursday, 16 May 2019 at 12:25:52 UTC, Suliman wrote: After 2 years dlang.ru was update. Content did not change. Main improves was is technology stack and design (still not perfect, but better than was). http://dlang.ru P.S. site is blocked by most of russian internet-providers by RKN Bullshit! I have checked the dlang.ru at RKN [1] registry and there are no dlang.ru in it. I checked with two providers from Russia and access works. Don't bug the forum with provocations or simply wait for DNS update. [1] - https://eais.rkn.gov.ru/ It was banned by IP. I checked it two weeks ago. It work very strange even from single mobile providers. https://imgur.com/a/NN3Apfo I do not think it is a fight against the opposition. For example, most of IP addresses of cloud service CloudFlare were blocked because of online casinos, which are banned in the Russian Federation. In fact, RKN does not block opposition websites. I recommend to host .ru sites at russian hosting companies. Because they take care that their IP addresses are not included in the RKN lists. Unlike, Tilaa. ;)
Re: dlang.ru is updated
On Saturday, 18 May 2019 at 06:26:10 UTC, Suliman wrote: On Saturday, 18 May 2019 at 03:01:33 UTC, 9il wrote: On Thursday, 16 May 2019 at 12:25:52 UTC, Suliman wrote: After 2 years dlang.ru was update. Content did not change. Main improves was is technology stack and design (still not perfect, but better than was). http://dlang.ru P.S. site is blocked by most of russian internet-providers by RKN Bullshit! I have checked the dlang.ru at RKN [1] registry and there are no dlang.ru in it. I checked with two providers from Russia and access works. Don't bug the forum with provocations or simply wait for DNS update. [1] - https://eais.rkn.gov.ru/ It was banned by IP. I checked it two weeks ago. It work very strange even from single mobile providers. https://imgur.com/a/NN3Apfo Well, yes this IP 37.252.127.244 is blocked for me and the checker [1] shows it belongs to dlang.ru (however the site itself works well). This was done by the court's decision [2] at 13.04.2018, more than a year ago. The information can be checked at [3]. You picked an already blocked IP. [1] https://ipinfo.info/html/ip_checker.php [2] https://www.mos-gorsud.ru/rs/taganskij/services/cases/civil/details/2cc72aea-39e7-4f8e-adc9-37d170966efa [3] http://blocklist.rkn.gov.ru/
Re: dlang.ru is updated
On Saturday, 18 May 2019 at 03:01:33 UTC, 9il wrote: On Thursday, 16 May 2019 at 12:25:52 UTC, Suliman wrote: After 2 years dlang.ru was update. Content did not change. Main improves was is technology stack and design (still not perfect, but better than was). http://dlang.ru P.S. site is blocked by most of russian internet-providers by RKN Bullshit! I have checked the dlang.ru at RKN [1] registry and there are no dlang.ru in it. I checked with two providers from Russia and access works. Don't bug the forum with provocations or simply wait for DNS update. [1] - https://eais.rkn.gov.ru/ It was banned by IP. I checked it two weeks ago. It work very strange even from single mobile providers. https://imgur.com/a/NN3Apfo
