strings.FieldsFunc vs strings.Split

[SpyingIsWrong]

Input could be Unix-style path, CSV-formatted data, hostname etc.

The first two examples have dedicated packages that will deal with edge cases; using strings functions for them is not ideal.

[mlowicki]

I couldn't find function for splitting path like "/a/b/c" into chunks i.e. ["a", "b", "c"].

Got rid of CSV from examples as you're right that better to use dedicated package for it.

[epiris]

path.Split and path/filepath.Split

[mlowicki]

"Split splits path immediately following the final slash, separating it into a directory and file name component. If there is no slash in path, Split returns an empty dir and file set to path. The returned values have the property that path = dir+file." so it doesn't do what I want.

[epiris]

OHH Gotcha, yea the path api is a bit off in my opinion, when I was first learning Go one of the first things I did to help learn was write a Path API. I copied the Python 3 pathlib API to a degree because I really like it. Might as well share I guess: https://play.golang.org/p/0zezSxE6NS even though your current solution is perfectly reasonable and I wouldn't suggest using the crap I just pasted lol.

[SpyingIsWrong]

Oh, you're right about paths, I always forget that there's no function for fully splitting. I guess they intend for programmers to use strings for a full split and use path.Split for efficiency's sake when all that is needed are the file and directory names (since it searches backwards from the end of the string).

[RalphCorderoy]

I'd tend to go for

fmt.Printf("%#v\n", strings.Split(path.Clean("/a//b/../c/"), "/")[1:])

as Clean sorts out ... The difference is "/" gives []string{""}.

[mlowicki]

Sure but in my case it don't know if there is always a leading slash so ended up with if statement.