Optimization Controls and Optimization Hints

[Arnold (Arnold Schwaighofer)]

@xwu

Should we consider, then, an orthogonal axis of the design, where this would be an expression-level annotation like unsafe and try rather than a block-level annotation? This would encourage more fine-grained specification of what exactly a user expects to be inlined.

Real-world usage may show it to be impractical, but at least the toy example given originally above—inline { call() }, and also by that token specialize { callSite() }—are more ergonomically spelled inline call() and specialize callSite().

Yes, that is a good question.

The ability to specify at a more fine-grained level which expression wants to be annotated makes sense to me as a good argument for preferring expression level annotations.

let expression = f() + (inline g())

The block level annotation version is more verbose and forces spelling of the type.

let temp : SomeType
inline {
  temp = g()
}
let expression = f() + temp