https://golang.org/doc/install/source does not document the folder hierarchy,
nor could I find it documented elsewhere.
Shouldn't we document the purpose of folders such as 'misc/'?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe
Yes, that was it! I reported upstream (Arch Linux) and it is now fixed.
Thanks!
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegro
5
```
Is this a bug?
--
Pierre Neidhardt
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I've developed a related bu complementary tool, also in pure Go:
https://ambrevar.bitbucket.io/hsync/
It synchronizes hierarchies, in the sense that it will detect renames and
move files on target accordingly, *without* transfering any file.
It can be a huge time saver in scenarios where renamin
use case where a Luar proxy should wrap more than one level
of indirection? E.g. if passed `**int`, should Luar wrap `**int` or `*int`?
I tend to think that Luar should always dereference until there is only one
level of indirection left.
Comments?
--
Pierre Neidhardt
--
You received this