[
https://issues.apache.org/jira/browse/ARROW-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16408665#comment-16408665
]
Stuart Carnie edited comment on ARROW-2335 at 3/21/18 10:10 PM:
----------------------------------------------------------------
[Damien Gryski|https://twitter.com/dgryski/status/976565595209519104] has
started a poll to see what other Go devs think, as there isn't a good precedent
for Go residing in multi-language repos. I still don't mind moving it back, but
I am interested in the results.
For some background, the current reason for using the {{.../go/arrow}} path is
so the Go package name of files in the {{arrow}} directory match. If we move
the files back to {{arrow/go}}, the directory of the files will be {{go}} and
the package name {{arrow}}, which is not the norm.
was (Author: stuartcarnie):
[Damien Gryski|https://twitter.com/dgryski/status/976565595209519104] has
started a poll to see what other Go devs think, as there isn't a good precedent
for Go residing in multi-language repos.
For some background, the current reason for using the {{.../go/arrow}} path is
so the Go package name of files in the {{arrow}} directory match. If we move
the files back to {{arrow/go}}, the directory of the files will be {{go}} and
the package name {{arrow}}, which is not the norm.
> [Go] Remove extra directory nesting from go/ directory
> ------------------------------------------------------
>
> Key: ARROW-2335
> URL: https://issues.apache.org/jira/browse/ARROW-2335
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Go
> Reporter: Wes McKinney
> Assignee: Stuart Carnie
> Priority: Major
> Fix For: 0.10.0
>
>
> I noticed this after merging. I am not sure we need the {{arrow/go/arrow}}
> directory structure if simply {{arrow/go}} would suffice
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
