Options parsing (and fromfile handling) is now entirely in Rust. So I’m not sure how to delegate reading the @fromfile to the scheduler.

One way is to pass references to Python’s underlying Scheduler and Session through to the native OptionsParser. But that means that the

options

crate would have to depend on the top-level engine crate, which in turn depends on basically everything, so I’m not sure that’s even possible.

I suppose it could be hidden behind an impl of a

FromFileReader

trait of some kind

But even then, can one use a Scheduler/Session to call an intrinsic directly in Rust?

(Reason to do so is to get the filewatching and subsequent invalidation of the fromfile)

Alternatively, now that options parsing is in Rust, and fast, maybe we don’t memoize options values via Python

memoized_property

and just recompute every time we read options?

Anyway, thoughts? Particularly from @witty-crayon-22786 ?

instead of

@memoized_property

, you would

.flat_map

(or

.and_then

for Rust name for it) the value to derive a new value

and depending on the context, the engine could have some way of knowing when one of the values changed

and then, yea: absolute file intrinsic

specifically: i think that you'll create the instance of the interface using the

Context

which is passed to some separate options parsing intrinsic