@Dennis Oh, alright. I probably should've tested it myself before asking anyway...

@Dennis Doesn't seem to work, this code should produce 'hello': tio.run/##JYxBCoAgFAX3nuLt0kUt2tcZuoLItwT1h1/…

$ cat > tio.coffee
test = ->
  new Promise (res) -> res 'hello'

main = -> console.log await test()

main()

$ coffee tio.coffee
hello

Because the token error occurs on the token after await, function in this case, I think this is still using CS 1.

@mınxomaτ CS 1 says ReferenceError: await is not defined.

Hm. I'm not able to repro the error I get on TIO with CS 2. I don't have CS 1.

CS 1: tio.run/##JYxBCoAgFAX3nuLt1EXdoM7QFUS@Jag//…

Maybe Node is too old.

I guess the double install borked references to other libs. Usually cs1 and cs2 cannot coexist.

@Dennis I'm using nvm to pin node to 8.4.0 here.

What's the TIO version?

Yep, that's it.

@mınxomaτ TIO has two Node versions: the system package (6.12 LTS), and a manual install in /opt (8.5.0). I added the latter to PATH and it prints hello now.

Maybe you could integrate nvm, and an UI option to switch between versions.

I'll look into that.

@Downgoat Done. I installed babel-preset-env instead of babel-preset-esXXXX, because that's what npm told me to do.

@Downgoat I avoid adding extra flags whenever I can. I've enabled command-line options for Babel Node though, so you can add whatever flags are pertinent.

@Dennis I can't get the Clean TIO to do anything with the header. What filename is it being given?

@Dennis also, the Clean compiler doesn't seem to have permissions on its own libraries: tio.run/##S85JTcz7/z83P6U0J1UhNzEzjysztyC/…

@Mego Done.

@Οurous Header, Code, and Footer get joined into a single file.

@Οurous Looks like Clean tries to build the libraries on first use. That's not possible, as the sandboxed compiler cannot make changes outside the home directory. I'll try to compile them during the installation process.

@Dennis Could you pull Alumin?

@ConorO'Brien Done.

@Dennis Hm, that doesn't work. It still tries to compile stuff in /opt at runtime...

The issue is that clm tries to recreate/modify the abc files, even if they already exist. One solution would be to copy everything from /opt/clean into the home directory, but I'd like to avoid that.

@Οurous tio.run/##S85JTcz7/z83P6U0J1UhNzEzjysztyC/…

Good thing I'm insane.

I always think I'll get away with it, but I never do...

@Dennis Thanks!

@Dennis thanks again! It needs three runs because it first compiles each file to .abc, then links each module into a full .abc file, then produces the .o files.

@Dennis could you please pull Chip when you get a chance?

@Phlarx Done.

@Dennis Thanks much!

@Dennis could you add the Platform library to the Clean install? Latest build is under ftp.cs.ru.nl/Clean/builds/linux-x64

@Dennis Oh, actually, it looks like TIO isn't using the iTasks environment for Clean, could you install clean-bundle-complete-linux-x64-latest as a replacement for the current install?

@Οurous That's a nightly build. Is there a reason the stable one won't work for TIO?

The executable from the nightly build hangs after clm: can't start the clean compiler: No such file or directory.

@Dennis The Nightly build is the only release with iTasks, which fixes a lot of bugs with fusion optimisation, has extended import syntax, and allows actually working world-state observation. It hangs because the entire bundle needs to go under the same directory. (Then set to CLEAN_HOME, as per the readme file)