Troels Henriksen

Sure, but all of those still involve machine-specific hand-tuning/scheduling (or search procedures). We don't have any current plans for Futhark to directly support that level of manual optimisation, but maybe...

I tried disabling the roundtrip entirely (thereby disabling rendering), and for some reason it did not become that much faster. Maybe this is not the bottleneck we think it is.

It would, but 1.5ms is not a lot, is all I'm saying.

Guess that must have broken along the way. It was always a bit of a hack... I wonder if we should just put Futhark exercises someplace else entirely.

To be honest, neither am I.

I have come to prefer this notation: ```Futhark #[tuning_param(my_important_parameter)] 100 ``` It will require an extension to the IR, as we need to make `GetSize` a `BasicOp`, but that is...

Another question is how/when to type check the default value. Maybe we need an actual language feature, instead of faking it via attributes.

Chapel's [config declarations](https://chapel-lang.org/docs/users-guide/base/configs.html#config-declarations-command-line-overrides) are very interesting, but perhaps overkill for our needs.

Requiring the attribute to be on a value definition might be a good idea, however.

@coancea we should talk about this one, since I remember you've wanted it before.