Reason: A new interface to OCaml • Hacker News Board

Re: Reason: A new interface to OCaml

#91

Post by bjz_ » Tue, May 17, 2016, 9:44 PM UTC

Would be nice to see modular implicits like those that are being proposed for OCaml. It's a shame to not have any form of ad-hoc polymorphism.

Re: Reason: A new interface to OCaml

#92

Post by ketralnis » Tue, May 17, 2016, 9:44 PM UTC

jordwalke wrote: post #25

kruhft wrote: post #6

Earlier quoted context omitted.

I was curious why it doesn't scroll. Barely works but gives a CPU spike and just jumps around between pages...

Chrome and Safari both worked for me. Common reports about Firefox, so I disabled the gif. Can you let me know if it works now?

Why does a text document describing a programming environment need to hijack scrolling at all?

Re: Reason: A new interface to OCaml

#93

Post by jordwalke » Tue, May 17, 2016, 9:44 PM UTC

ulber wrote: post #42

This page is completely unusable due to lag. From the other comments it seems this is FF specific. One would think FB would have the resources to test new pages at least on common browsers before publishing. Edit: The fix came quickly though.

Cheng Lou fixed the firefox issue. Refresh and it should be fixed. Thanks again for reporting.

Re: Reason: A new interface to OCaml

#94

Post by SilasX » Tue, May 17, 2016, 9:45 PM UTC

jordwalke wrote: post #82

saticmotion wrote: post #72

Earlier quoted context omitted.

Disabling the box shadow on .content-root fixes the performance bug (FF46.0).

We just discovered the same by disabling the media query which handles the shadow. Thank you very much for investigating.

Seems to work fine on FF (46) now, thanks.

Re: Reason: A new interface to OCaml

#95

Post by chenglou » Tue, May 17, 2016, 9:46 PM UTC

bjz_ wrote: post #91

Would be nice to see modular implicits like those that are being proposed for OCaml. It's a shame to not have any form of ad-hoc polymorphism.

Reason will have modular implicit. It's really just OCaml under the hood.

Re: Reason: A new interface to OCaml

#96

Post by bjz_ » Tue, May 17, 2016, 9:47 PM UTC

stuartaxelowen wrote: post #56

Can we please keep using parens for function invocation? Leaving them out hurts readability.

The difference between curried langs like OCaml and Haskell and languages like Ruby and Elixir are that the leaving out of parens actually means something, ie. all functions take one argument. If you wanted parens whilst maintaining the same semantics, you would end up having to do write: `add(2)(3)`

Re: Reason: A new interface to OCaml

#97

Post by zem » Tue, May 17, 2016, 9:47 PM UTC

i noticed this in the examples:

    | List p (List p2 (List p3 rest)) => false  /* 3+ */

has the regular list destructuring in pattern match syntax been removed? that's pretty sad, if so - lists are the default data structure in ocaml, and it's worth retaining some special syntax for cons especially in pattern matches.

Re: Reason: A new interface to OCaml

#98

Post by jordwalke » Tue, May 17, 2016, 9:50 PM UTC

stuartaxelowen wrote: post #56

Can we please keep using parens for function invocation? Leaving them out hurts readability.

Please take a look at the FAQ which describes the best way to move forward with evolving the syntax. It helps to know your personal technical background and where you're coming from, as well. I do like your idea, but you can currently use parens - it's just that they aren't required by the parser when the argument is clearly one item (like an integer constant etc). Then at that point, it's just a matter of configuring the source formatter to always include them.

Re: Reason: A new interface to OCaml

#99

Post by dmm » Tue, May 17, 2016, 9:50 PM UTC

Paul_S wrote: post #55

jordwalke wrote: post #28

Earlier quoted context omitted.

Sounds like FF can't handle gifs, but Chrome/Safari do a good job. I've disabled the gif on the main page just to be friendly to FF while I figure out a better approach. Thanks for the report.

I can run the Unreal engine, use google maps but not view your website. I'm not convinced Firefox is at fault here. Is there any interactive functionality that your website offers that would justify extraordinary demands or does it simply display some text and images?

He has an onscroll event that is causing a ton of redraws.

Re: Reason: A new interface to OCaml

#100

Post by MichaelGG » Tue, May 17, 2016, 9:51 PM UTC

I started off a bit skeptical with the What's OCaml's status with multithreading? Are there any proposals for more flexible operators, so there doesn't need to be different operators for different numerics? (F# solves this by allowing inlined functions.)