Correct - there has to be a clear indication that you are consenting. It can't just be hidden away in a 60 page document in a statement that says "I consent to being tracked, etc".
Could you elaborate what issues does it come with? I'm biased since I grew up in an area with street names and a consecutive system, but genuinely interested in hearing more.
It's a hassle to have your address changed with every service that wants to send you mail (landlord, utilities, government offices, online shops, magazine subscriptions, etc.), so the change must be considered more valuable than this cost.
In the best case scenario they are very safe choices, that are then reused basically everywhere, sometimes in several places in the same town.
I have seen countless of french towns with "Général de Gaulle" named variations of streets, places, rotaries, small passages etc. It's so overused that it doesn't make sense anymore, people mess with the categories very often (was it a street or a boulevard ? who cares ?)
In the worst case scenario, street names are chosen according to the heroes of the times, or some other political figure that is/will be highly controversial once it has its name on a plaque.
It then becomes an endless battle to find a compromise, avoid further cultural frictions while choosing names that make sense for the town.
For instance in former colonies, street names have often been set to colonial personalities. Some of the (wealthy) residents still support the naming, while others (sometimes minorities) will object to the cultural signification of having these names around for public areas.
These issues are just symptoms of deeper problems, but not using names in the first place just makes things easier.
The idea of avoiding context switches by using memory regions to communicate with the kernel reminds me of FlexSC[0], which was a way to have "async" system calls and "flexible scheduling" of them.
I've never totally followed why AIO is its own set of interfaces instead of a generic async system call mechanism based on something like this. Write a bunch of requests to a page in the form of the registers that would make up the syscal, then wait for one to be completed using a futex or something (where futex(2) remains an actual system call).
Does vim-racer[0] not work for you? I don't exactly know what you mean by "good autocomplete", but if you are more specific, then maybe we can help you a little more? :-)
FWIW, my Rust setup in vim is mostly the following plugins:
* NERDCommenter, for commenting stuff
* rust.vim, for general rust things (like integration with rustfmt, playground, and the next two plugins)
* tagbar, for showing the list of tags (of the ctags-esque sense) in a sidebar.
The contortion required to get your pinkie up to escape versus just pressing caps lock is pretty significant. Some people say that they get “vim pinkie” RSI as a result of making that awkward movement, the same as Emacs pinkie on Ctrl in the bottom left.
