@Dennis FYI, the code textarea doesn't autofocus for me either. Seems to be because my laptop is being detected as a touch device (which technically it is).
Oddly enough this is only a problem on Firefox. On Chrome and Edge the touch functionality doesn't appear to be detected so the autofocus works.
Hm. I wanted to avoid getting half of your phone's screen covered with a keyboard that you may not use, but I didn't even think of traditional computers with touch functionality. I'll try to think of a better way to make that decision.
The things I install through these packages managers are the ones that get updated the least. I have no experience with opam in particular, but there's usually no easy way of updating everything, and no easy way to roll back if an update went bad.
I couldn't find an F* HW, and print seemed to require an import, so I spent around 10 minutes guessing module names until I found something that works.
module Main
open FStar.IO
let main = print_string "hello"
As has been pointed out in the comments, ; is not a statement terminator like in many other (Algol-inspired) languages, but a sequence operator. It takes two values, throws away the first (but warns if it is not unit) and returns the second. a; b is therefore roughly equivalent to let _ = a in b....
@JamesHolderness well if you go to a computer store (at least the case for me) most of the displayed computers are touch capable. firefox is a pretty popular browser, so it's not too unreasonable
I didn't realize Safari was becoming such a major player in the US and (to a lesser degree) Europe. I literally don't know people in this country who use Apple devices...
@Dennis I feel like TIO had this at one point (or it was discussed), but do you ever plan on adding language specific highlighting tags to the code golf submission formatter? e.g. <!-- language-all: lang-mathematica --> for mathematica
@Dennis Hi @Dennis -- Thanks for thinking to ask. It should "just work" and seems to be. This program reports how many processing units (PUs) the node has and is correctly reporting two: tio.run/##S85ILEjN@f@/vCizJDUnTyMjtShVL680NyC0WENT0/r/fwA
I was trying to puzzle why the parallel loop was seemingly getting split into four chunks rather than two (note that 1..25, 26..50, 51..75, 76..100 are interleaved consecutively in the output depending on how things are scheduled) and remembered that we'd artificially set it to use 4 threads to make it more interesting even with one core: github.com/TryItOnline/tryitonline/blob/master/wrappers/chapel
So, we could stop setting QT_HWPAR in the environment, and I believe we'd see it split the parallel loop into two chunks instead (1..50 and 51..100 would be interspersed).
I don't feel strongly about which way it's configured. Not setting the variable would be more "normal" (we tend to use a number of threads/tasks equal to the number of cores by default), but using 4 threads/tasks is slightly more "interesting"? Your call.
Wolfram Language 11.2.0 Engine for Linux x86 (64-bit)
Copyright 1988-2017 Wolfram Research, Inc.
You will need to get a password from your
license certificate or from Wolfram Research
(register.wolfram.com).
Enter your name:
Enter the name of your organization:
Enter your password:
The password you entered is not valid.
Please press Enter to quit.
This is what I get as output regardless of the code
talk.tryitonline.net
talk.tryitonline.net