Philip Munksgaard

Perhaps something for @WilliamDue?

[Here](https://github.com/integer32llc/rust-playground#resource-limits) is some information about the limitations imposed on the [Rust playground](https://play.rust-lang.org). I'm not sure how that is enforced, but presumably one could glean that information from the repo somewhere.

As compromise, would it make sense to _compile_ the program on our machines, but _run_ it in the browser, using e.g. our wasm backend? Would that even work? Edit: In...

Good idea! Pull requests are certainly welcome, but I cannot promise that anyone else is going to come around to adding it anytime soon.

I've also been bitten by this. As a quick workaround, I decided to vendor the dependencies and add them to my git repository, but I'd be really interested in a...

Perhaps an alternative would be to extend trybuild? It already has the basic features of compiletest, but is more self-contained.

I dream about doing an entire merge from upstream, you can see my progress in #201. However, this will remove the `run-pass` test mode. It seems like `ui` is used...

> @Munksgaard can we test this with the `ui` tests that compiletest already supports? IIRC a lot changed there upstream so I am not sure if that is a representative...

Hi @karlosss, Unfortunately, this PR mostly serves as a (pretty outdated) mirror of [rusts builtin compiletest](https://github.com/rust-lang/rust/tree/master/src/tools/compiletest), so we don't generally add features not present there. I encourage you to either...

Our [session-types library](https://github.com/Munksgaard/session-types) also broke due to the recent changes in compiletest. Your changes seem to fix some of the issue, but I'm still getting the following errors when trying...