Marcelo Cantos

That would create more work for users and more opportunity to accidentally use an old PAC, which would be confusing and difficult to diagnose.

At the end of the day, this really should be fixed at the source. How about just requiring https:// or `--unsafe-proxy-pac-url http://…`?

Based on [github.com/Homebrew/brew/…/service_spec.rb](https://github.com/Homebrew/brew/blob/9657303ed2c484a4bd8f7527706940f9e4d43354/Library/Homebrew/test/service_spec.rb#L117-L118), perhaps you could log to `#{HOMEBREW_PREFIX}/var/log/alpaca.log`. I don't know how (or whether) `HOMEBREW_PREFIX` is populated, however.

https://docs.google.com/document/d/1utARjjIXTKQCRQ6Zsrdp5WO3FRAsZnF5VKZG41UObF4/edit?usp=sharing

Another use case in response to majek's question: sending protocol buffers between servers, modern browsers, and native mobile apps. I want to use SockJS for its solution to the fallback...

A simple workaround is `local core = core.v1`, or even `local c = …`.

You wouldn't define `local container = …`, just use `core.container` or `c.container` everywhere.

Would JavaScript destructuring syntax work? ```javascript local { container, claim, … } = core.v1; ```

Technically, it's not a sequence. In JavaScript, {a:1, b} is shorthand for {a:1, b:b}. Destructuring assignment reuses the same pattern.

If you're going to go down this path, several elements could be considered in addition to the above suggestions: 1. Optional **attribute:variable** syntax: `local {a:x} = {a:1}` is equivalent to...