Trait-based dispatch for eos types?

[stepanzh]

Perhaps, for eos implementation it is better to use trait-based dispatch. That would free eos-developer from subtyping of AbstractEoSComponent/Mixture.

[vvpisarev]

Any specific example of what doesn't fit into the subtyping model?

[stepanzh]

I imagine if there is a package FooEoS.jl outside CubicEoS.jl infrastructure which implements a FooEoS. If a user wants to use FooEoSType from the package and CubicEoS.jl solvers, the user has to dev the package and "inject" our subtyping to existing codebase. In case of trait-base dispatch, such user only has to implement an interface layer to use CubicEoS solvers.

Subtyping model forces users to implement eos by our rules, making the whole infrastructure "closed". It's OK, when the eos is implemented from scratch and would be used only with CubicEoS. On other hand, trait-based model is more flexible and adaptive both to new and existing codebase.