Document core autocons

[courajs]

Found in the wild: https://github.com/Fang-/djay/blob/261766af0383eaa6f1e168b6c4c06da69a64175e/app/djay.hoon

[anonymous]> yeah, it gets treated as equivalent to => |% ... -- |_ ... --

Not mentioned in the bar rune reference or the irregular form reference.

[ohAitch]

Nor the ford reference? This isn't specific to bar runes

…

On Wednesday, 17 April 2019, Aaron Sikes ***@***.***> wrote: Found in the wild: https://github.com/Fang-/djay/blob/ 261766af0383eaa6f1e168b6c4c06da69a64175e/app/djay.hoon ~palfun-foslup> yeah, it gets treated as equivalent to => |% ... -- |_ ... -- Not mentioned in the bar rune reference <https://urbit.org/docs/reference/hoon-expressions/rune/bar/> or the irregular form reference <https://urbit.org/docs/reference/hoon-expressions/irregular/>. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <https://github.com/urbit/docs/issues/465>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABxXhqjUUsLqrEjiDHcy2Z6jRvsfXQlkks5vhx8kgaJpZM4c1CP2> .

[rmariani]

Thanks for catching this, I will look into it.

[baudtack]

@Fang- Is this only a thing in gall apps?

[Fang-]

Not sure, but would be surprised if it's special-cased like that. Probably just a compiler thing?

[ohAitch]

Yes, the ford parser effectively wraps the whole file in a =~ ... ==

[belisarius222]

@ohAitch is correct. This is behavior specific to the Ford parser, not a compiler feature. If you're writing a file that Ford does not compile, such as a vane, you have to have a single Hoon expression instead of a list of them.