Closed mlange-42 closed 3 years ago
@adamreichold Realized that starting to crack settings out of the parser might motivate that all settings become just ParserSettings
. Then, the MdParser
could go away completely, and everything inside could become simple module functions. So maybe this should be done during/after the general restructuring (#57)?
So maybe this should be done during/after the general restructuring (#57)?
It is certainly aligned with that approach, but I would not make it dependent on that refactoring. There is also an intermediate state where the parser settings are within a ParserSettings
struct in the config
module and MdParser
is unit-like struct without any fields.
Already implemented as an intermediate state in #75.
Decided to remove that feature completely.
Meta variables should not be allowed by default.
Make it a feature to be explicitly activated, e.g. by wrapping the three related
toml
options into an optional struct. Should we then detect if it is enabled and any language is set up for reverse mode, and emit a warning?Also mention the limitation is the guide.