The definition of VLSM_incl is pretty awkward, because of the need to share the VLSMType common to both arguments. This causes various issues, including big terms appearing when applying related lemmas, having to manually apply lemmas for symmetry or transitivity, etc. There were some improvements already (PR #193) and some attempted improvements (PR #199), but the situation can still be improved.
Some of the possible tasks include:
The definition of
VLSM_inclis pretty awkward, because of the need to share theVLSMTypecommon to both arguments. This causes various issues, including big terms appearing when applying related lemmas, having to manually apply lemmas for symmetry or transitivity, etc. There were some improvements already (PR #193) and some attempted improvements (PR #199), but the situation can still be improved.Some of the possible tasks include:
VLSM_incl_refl,VLSM_incl_symandVLSM_incl_transinto instances ofReflexive,SymmetricandTransitive(and likewise for similar lemmas forVLSM_eq,VLSM_embedding, etc.) - this should be the simplest taskVLSM_inclbased onVLSMMorphism