On Tuesday, 5 January 2021 at 21:46:46 UTC, H. S. Teoh wrote:
implemented, rather than the concept of exceptions itself. If
we implement Sutter's proposal, or something similar suitably
adapted to D, it would eliminate the runtime overhead, solve
the @nogc exceptions issue, and still support
On Tuesday, 5 January 2021 at 22:01:08 UTC, Ola Fosheim Grøstad
wrote:
Also, I think this is better determined using whole program
optimization, the chosen integer bit pattern used for
propagating errors has performance implications. The most
freguently thrown/tested value should be the one
On Tue, Jan 05, 2021 at 06:23:25PM +, sighoya via Digitalmars-d-learn wrote:
> Personally, I don't appreciate error handling models much which
> pollute the return type of each function simply because of the
> conclusion that every function you define have to handle errors as
> errors can
On Monday, 4 January 2021 at 17:17:10 UTC, Steven Schveighoffer
wrote:
On 1/2/21 12:52 PM, Selim Ozel wrote:
After logging into to 127.0.0.1 for a single time in my
browser, if I do a ctrl+c it still leaks two socket handles.
With connection Windows 10:
Running .\vibe_noleaks.exe
On Sunday, 3 January 2021 at 23:53:54 UTC, aberba wrote:
On Friday, 1 January 2021 at 22:07:28 UTC, Selim Ozel wrote:
I created the simplest possible example as explained by the
Vibe-D community in [1]. The exact source code of what I run
is in [2].
On Windows I get a socket handle leak
On Tuesday, 5 January 2021 at 19:42:40 UTC, Ola Fosheim Grøstad
wrote:
On Tuesday, 5 January 2021 at 18:23:25 UTC, sighoya wrote:
No error handling model was the HIT and will never be,
therefore I would recommend to leave things as they are and to
develop alternatives and not to replace
On Tuesday, 5 January 2021 at 18:23:25 UTC, sighoya wrote:
No error handling model was the HIT and will never be,
therefore I would recommend to leave things as they are and to
develop alternatives and not to replace existing ones.
Or implement C++ exceptions, so that D can catch C++
Bye bye nothrow functions in Dlang.
On Monday, 4 January 2021 at 15:39:50 UTC, ludo456 wrote:
Listening to the first visioconf of the Dconf 2020, titled
Destroy All Memory Corruption,
(https://www.youtube.com/watch?v=XQHAIglE9CU) Walter talks
about not using exceptions any more in the future. He says
something like "this is
Personally, I don't appreciate error handling models much which
pollute the return type of each function simply because of the
conclusion that every function you define have to handle errors
as errors can happen everywhere even in pure functions.
You don't believe me? What about memory
10 matches
Mail list logo
