Skip to content

Thoughts on Notation

Jump to bottom
Laird Nelson edited this page Oct 22, 2021 · 2 revisions

See Thoughts on Paths for some background.

See Thoughts on Providers for further background.

There needs to be notation for a provider to express a set of compatible paths. The notation for paths is already pretty far along.

The first case that bubbles up to the top is a provider wanting to say: "I provide Cylinders for any Car's Engine when the application is qualified with env=test and possibly other qualifiers" where the demand is car.getDrivetrain().getEngine().getCylinder(0).

Brainstorms:

  1. /:env=test/.../Car.class/.../Engine.class/Cylinder.class
  2. …actually that's pretty good.

... says "contains", and the ordering is nice. So: a path that starts with an application qualified with env=test, followed by whatever, followed by Car.class in there somewhere, qualifiers don't matter, followed somewhere further on by Engine.class/Cylinder.class followed by the end.

Clone this wiki locally