From the docs:

Note: writing plugins requires accessing the compiler APIs. This API has a very large surface area, so we cannot guarantee that these APIs won't change in the future.

Understood, though providing a stable API someday would be awesome.

My shorter-term concern is that you'd have to provide different versions of your plugin for different versions of Fan. That could get ugly.

Would it be possible somehow to get around this? Compiling different code compatible with different versions and sticking it all in the same pod seems a bit nasty, I have to admit. I'm not sure what's best. Just bringing up the question.

Side note, it says "Pluging" instead of "Plugin" at one point on the DSLs doc page.

My shorter-term concern is that you'd have to provide different versions of your plugin for different versions of Fan. That could get ugly.

Once we ship 1.0, all APIs will be locked down. And I doubt we will change it much after 1.1 or 1.2 settles down. So at worse you might 2 or 3 versions, and even that is doubtful, because as such a new language I doubt people will standardize on an older version. We'll have to see what kind of ecosystem developers around the compiler API.

Side note, it says "Pluging" instead of "Plugin" at one point on the DSLs doc page.

fixed, thanks

Okay. Thanks for the road map and ideas.