The perfect programming language

Post by abathologist » Fri, Nov 15, 2019, 8:40 PM UTC

tome wrote: post #72

abathologist wrote: post #48

Earlier quoted context omitted.

> The moment you allow imperative behaviors to leak into a declarative system it loses its ability to reason reliably about operations over time; and you’re back to flying seat-of-your-pants a-la C &co By your (imo, extremist) line of reasoning, wouldn't the existence of `unsafePerformIO` mean Haskell itself "looses its ability to reason reliably about operations over time"? I think a more reasonable position allows…

> By your (imo, extremist) line of reasoning, wouldn't the existence of `unsafePerformIO` mean Haskell itself "looses its ability to reason reliably about operations over time"? By your (imo, extremist) line of reasoning, wouldn't the existence of `unsafePerformIO` mean Haskell itself "looses its ability to reason reliably about operations over time"? Well no, because for some reason, be it social or technical, peopl…

Post by daotoad » Fri, Nov 15, 2019, 10:10 PM UTC

    multi sub fb( Int $n where * %% none(3,5) ) { return $n }
    multi sub fb( Int $n where * %% all(3,5) )  { return 'fizzbuzz' }
    multi sub fb( Int $n where * %% 3 )         { return 'fizz' }
    multi sub fb( Int $n where * %% 5 )         { return 'buzz' }

    .say for (1..15).map({ fb($_) } );

    subset Fizzy of Int where * %% 3;
    subset Buzzy of Int where * %% 5;
    subset FizzBuzzy of Int where * %% (3&5);
    subset Otherwyzy of Int where not * %% (3|5);

    multi sub sfb( Otherwyzy $n ) { return $n }
    multi sub sfb( FizzBuzzy $n ) { return 'fizzbuzz' }
    multi sub sfb( Fizzy $n ) { return 'fizz' }
    multi sub sfb( Buzzy $n ) { return 'buzz' }

    .say for (1..15).map({ sfb($_) } );

Post by majewsky » Fri, Nov 15, 2019, 11:03 PM UTC

pjmlp wrote: post #78

majewsky wrote: post #76

Earlier quoted context omitted.

Is it fair to compare GUI frameworks with over 20 years of maturity (Qt, GTK+) with others that are less than a few years old and still mostly in their exploratory stages?

It is, because the issue is the language semantics to deal with typical UI workflows. You are forced to use Rc > and clone everywhere, or copy objects around, reactive style, to kind of work around borrow checker ergonomics.

Post by Gibbon1 » Fri, Nov 15, 2019, 11:34 PM UTC

MaxBarraclough wrote: post #84

Gibbon1 wrote: post #13

Earlier quoted context omitted.

> c++ has a awful compile time I have a thoery that C++ compiler writers obsession with pointless micro optimizations is because C++'s compilation model scales horribly. Thus they desperately want their compiler to be faster. But they are fucked because the more optimizations just slows down the compile times even more.

You can disable optimisation if you want faster builds. The existence of optional optimisations isn't a problem.

Post by Mikhail_Edoshin » Sat, Nov 16, 2019, 5:58 AM UTC

ebruchez wrote: post #65

hyperpallium wrote: post #37

Earlier quoted context omitted.

XSLT syntax (x < 10) would be its worst problem, except for its other problems. But seriously, XSLT's recursive templates are a nice idea for transformation, and the homoiconicism enables transformation of XSLT stylesheets theselves.

You can write `x lt 10` since XSLT 2.0 in 2007.