<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Nov 1, 2020, at 5:41 AM, Simon Marlow <<a href="mailto:marlowsd@gmail.com" class="">marlowsd@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Richard, what do you think?</span></div></blockquote></div><br class=""><div class="">I tend to agree that keeping defaults consistent is a good idea. I think that, subconsciously, the reason I designed the proposal the way I did was because I think the default of unqualified is wrong. But that's not a battle I wish to fight, and this kind of consistency has real merit. When I take a pass through the proposal to update it, I'll either add this (making unqualified the default for the new features) as a fleshed out alternative or incorporate it directly, depending on which would read more easily.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Richard</div></body></html>