[go-nuts] Re: import paths - slash vs backslash

2018-02-20 Thread Volker Dobler
On Friday, 10 November 2017 19:31:37 UTC+1, Tim Hockin wrote: > > Is it valid to say `import "github.com\foo\bar" (windows path > separators) or must it be "github.com/foo/bar"? I couldn't find a > canonical answer to this. > Using backslashes as a path separator is wrong on Windows too. Just

Re: [go-nuts] Re: import paths - slash vs backslash

2018-02-19 Thread Ian Lance Taylor
On Mon, Feb 19, 2018 at 9:15 PM, 'Tim Hockin' via golang-nuts wrote: > Pinging this topic - does anyone know? > > On Fri, Nov 10, 2017 at 10:30 AM, Tim Hockin wrote: >> Is it valid to say `import "github.com\foo\bar" (windows path >> separators) or must it be "github.com/foo/bar"? I couldn't fin

[go-nuts] Re: import paths - slash vs backslash

2018-02-19 Thread 'Tim Hockin' via golang-nuts
Pinging this topic - does anyone know? On Fri, Nov 10, 2017 at 10:30 AM, Tim Hockin wrote: > Is it valid to say `import "github.com\foo\bar" (windows path > separators) or must it be "github.com/foo/bar"? I couldn't find a > canonical answer to this. > > Thanks > > Tim -- You received this mes

[go-nuts] Re: import paths - slash vs backslash

2017-11-10 Thread Dave Cheney
That's a good question. The contents of the import declaration are defined to be implementation dependent by the spec > The interpretation of the ImportPath is implementation-dependent but it is typically a substring of the full file name of the compiled package and may be relative to a reposi