Hi everyone! So I'm still playing with `eval`, is...

# arrow-meta

[Ahmed Mourad]

Hi everyone!

So I'm still playing with eval, is there a way to use the classpath of the plugin consumer during the evaluation?

[Ahmed Mourad]

As in, if the consumer writes something like this:

[Ahmed Mourad]

I'd like to be able to use Password during the evaluation.

[raulraja]

Password is not resolved when that gets evaluated at compile time. This is why the validate function in the type refinements in meta is pure

[raulraja]

And only refers to types that are available in the compiler classpath

[raulraja]

In this case it would expect the receiver to be a String and that's all you can resolve at compile time because the compiler classpath includes the std lib.

[raulraja]

You can workaround this limitations with your own types if they come from already compiled modules and you expose those in the kotlinCompilerClasspath but not with the same type you are refining in a local module.

[raulraja]

TLDR you can use third party compiled libs inside eval but not local module types you are refining in place

[raulraja]

If you figure it out then we want it in meta too 🙏

[Ahmed Mourad]

How unfortunate. I'll see what I can do, if I find something, I'll let you know.

[raulraja]

You can potentially use your type on eval if you add a version of it to the eval session as a declaration. That is declare Password and eval it without the constrains once in the session

[raulraja]

Then use the lightweight declaration in the compile time validation.

[Ahmed Mourad]

Sounds interesting, the only problem would be if Password used other locally declared classes.

But I guess I could through those recursively as well until only third party types are left.