@MDXF I'm not brilliant at bash, but I think you want those backticks in the wrapper surrounded by double quotes so whitespace doesn't split it into multiple arguments.
Also, you might as well stick -march=native into the compiler flags.
@MDXF I appreciate the intention to include a wrapper, but I won't be able to use it in its current form, as it requires cd-ing into the repo.
A wrapper that makes no assumptions about the CWD, hardcodes no filenames, reads from STDIN, and doesn't clobber any files when compiling could look like this.
@Οurous Allows the compiler to make use of features available on your specific CPU architecture to run faster. Code compiled with -march=native will likely not run on any other computer with a different cpu.
Code compiled on TIO has no reason not to use it, since the binary can't be reused anywhere else and it doesn't really make compilation take long.
At the moment the language comes as a container that you pipe the code into, it runs it and outputs the output, I guess for TIO the overhead of spinning up a container would not be ideal, and a script would be a better option, as dependencies are shared with other languages
@jrtapsell I'm not even sure if that would work inside the sandbox. I have no experience with containers, but if they require Unix sockets, I won't be able to use them.
talk.tryitonline.net
talk.tryitonline.net