Commits on Jun 2, 2023

1. Backout Unicode bare keys …

   This backs out the unicode bare keys from toml-lang#891.
   
   This does *not* mean we can't include it in a future 1.2 (or 1.3, or
   whatever); just that right now there doesn't seem to be a clear
   consensus regarding to normalisation and which characters to include.
   It's already the most discussed single issue in the history of TOML.
   
   I kind of hate doing this as it seems a step backwards; in principle I
   think we *should* have this so I'm not against the idea of the feature
   as such, but things seem to be at a bit of a stalemate right now, and
   this will allow TOML to move forward on other fronts.
   
   It hasn't come up *that* often; the issue (toml-lang#687) wasn't filed until
   2019, and has only 11 upvotes. Other than that, the issue was raised
   only once before in 2015 as far as I can find (toml-lang#337). I also can't
   really find anyone asking for it in any of the HN threads on TOML.
   
   Reverting this means we can go forward releasing TOML 1.1, giving people
   access to the much more frequently requested relaxing of inline tables
   (toml-lang#516, with 122 upvotes, and has come up on HN as well) and some other
   more minor things (e.g. `\e` has 12 upvotes in toml-lang#715).
   
   Basically, a lot more people are waiting for this, and all things
   considered this seems a better path forward for now, unless someone
   comes up with a proposal which addresses all issues (I tried and thus
   far failed).
   
   I proposed this over here a few months ago, and the responses didn't
   seem too hostile to the idea:
   toml-lang#966 (comment)

   

   arp242 committed Jun 2, 2023
   Configuration menu

   • View commit details
   • Copy full SHA for 3201e86
   • Browse repository at this point

   Copy the full SHA

   3201e86 View commit details

   Browse the repository at this point in the history