nvda

5a4512ef - Add notes on limitations to retaining backwards compatibility (#14049)

Add notes on limitations to retaining backwards compatibility (#14049) See also #14050 Summary of the issue: #14037 was closed because there was no way to preserve backwards compatibility. This is the case for any module level variable which the NVDA API expects to support assignment. Description of user facing changes None Description of development approach Documentation has been added: to warn developers about writing code which allows for future changes without breaking backwards compatibility. keep track of cases which we cannot safely retain backwards compatibility, so that we can clearly define when API breaking changes are necessary