March 04, 2022

On Sunday, 27 February 2022 at 10:16:23 UTC, Paulo Pinto wrote:

>

By the way, NVidia now has a A Team collection of C++ people, it is quite clear that C++ has won the wars of programming GPU hardware and SYSCL will cement the same for FPGA design.

I think that that is not at all the case. If anything its more that CUDA has won in the GPU space, to the detriment of OpenCL, because of its relative ease of use.

March 04, 2022

On Friday, 4 March 2022 at 03:42:04 UTC, Nicholas Wilson wrote:

>

On Sunday, 27 February 2022 at 10:16:23 UTC, Paulo Pinto wrote:

>

By the way, NVidia now has a A Team collection of C++ people, it is quite clear that C++ has won the wars of programming GPU hardware and SYSCL will cement the same for FPGA design.

I think that that is not at all the case. If anything its more that CUDA has won in the GPU space, to the detriment of OpenCL, because of its relative ease of use.

Be as it may be, C++ found its niche, like SQL on RDMS, and NVidia employs quite a few ISO C++ contributors.

March 04, 2022
On Thursday, 3 March 2022 at 15:35:03 UTC, Paul Backus wrote:
> On Thursday, 3 March 2022 at 12:05:11 UTC, Atila Neves wrote:
>> On Friday, 25 February 2022 at 00:30:49 UTC, H. S. Teoh wrote:
>>>
>>> Go, Zig, Rust, and Odin all require explicit checking for error returns.
>>
>> Nope: http://web.mit.edu/rust-lang_v1.25/arch/amd64_ubuntu1404/share/doc/rust/html/reference/expressions/operator-expr.html#the-question-mark-operator
>>
>> Years ago, I justified my preference for exceptions because the rest of the call stack didn't have to be cluttered with "rethrowing". Having to pattern match is better, but still a pain. The macro solution they went with is the only one I know of that is as easy to use as exceptions without the associated baggage.
>
> Swift has similar syntax sugar with its "try" keyword:
>
> https://docs.swift.org/swift-book/LanguageGuide/ErrorHandling.html
>
> And of course there are also more general-purpose language features like Haskell's "do" notation [1] and Scala's "for" comprehensions [2] that handle this as a special case.
>
> [1] https://en.m.wikibooks.org/wiki/Haskell/do_notation
> [2] https://docs.scala-lang.org/tour/for-comprehensions.html

I didn't know about Swift, thanks for the link.

I left out Haskell on purpose - do notation can do "anything" for certain values of "anything". Then people stack monad transformers 4 deep and I'm off to the hills. Or would be if I wrote Haskell, there's a reason I don't.
March 04, 2022
On Thursday, 24 February 2022 at 03:42:42 UTC, SealabJaster wrote:
> ...
> On a similar vein, if we have that sort of `catch expression` shown above, we could possibly make our own version of `if err != nil` spam look even worse :D!
>
> ...
>
> if(toInt("123") catch(ex) + toInt("abc") catch(ex) && ex.isError)
> {
>     writeln(ex.msg);
>     return -1;
> }
> ```
>
> But the point is, if we want to avoid Go's if-else spam, we need some other weird syntax to sugar on top of things.

Hey...let's just go crazy, and borrow some bew syntax from the .net team (bang..bang !!)

// don't ask me what this would do... I don't care.
if( toInt("123")!! + toInt("abc")!!)
{
   writeln(ex.msg);
   return -1;
}

Seriously, when will this obsesssion with constantly changing languages..stop!

D... plz learn the lessons from the silly .net team... I no longer even recognise C#

https://devblogs.microsoft.com/dotnet/early-peek-at-csharp-11-features/

1 2 3 4 5 6 7 8 9 10 11
Next ›   Last »