Rob
I thought it might be an operator precedence issue; but putting each clause in its own parentheses group still hints at the bug.
The ones listed in the README as "excluded". They are not actually currencies, but more like trading units and such. Possibly used on stock markets and the like.
@kashukov ESA is historical and not part of the current list. SVC seems to be missing indeed.
1. I have never seen someone name a file and ending the name with a trailing space. Sounds like an exotic edge-case that nobody cares about me thinks. "Blindly" using...
`@stable` is not exactly a version constraint, it's rather a stability flag. I think it could be adjusted though to pick the latest, rather than the earliest. Something like `findBestVersionForPackage()`...
For proxy issues, try: https://gist.github.com/naderman/377e40c1c76e0fe8b905c1a333c4112a Details: https://twitter.com/naderman/status/1029839134070853637
I personally think the whole `global` flag/command is a painful source of confusion either way. I understand it has its use-cases, but in general I think most people have different...
@seldaek quite a lot of people who are new to composer quickly/often relate it to npm's global. Which is quite different..
A global install on npm also means you could use it locally though, doesn't it?
Well, the `Composer\Autoload` namespace exists already (see `src/Composer/Autoload`). Perhaps something that makes it easier to separate from the existing namespaces, `Composer\Generated` or `Composer\Vendor\Autoload`?