syntax_data: {"ast_node_type":"other","tokens":[{"end":93,"kind":"keyword","start":0,"text":"//!"}]}
source_snippet: //! only benefit would be the ability to check that the least upper (or greatest lower) bound
context_before: //! dataflow analysis, there's no need for a newtype wrapper with a custom `PartialOrd` impl. The
context_after: //! returned by the lattice join (or meet) operator was in fact greater (or lower) than the inputs.