On Tuesday, February 20, 2018 at 2:00:32 PM UTC-7, Jan Mercl wrote: > > > I don't know how the concept of word got involved in the "expected" > behavior, but the code shown has nothing to do with something like "word". > It works purely with strings and slices of strings and is AFAICT working as > intended. >
Ah. It just dawned on me what is going on. Since the .Split function didn't encounter a '/' between the "that there" & "here that", both of those are subsequently evaluated as the s1 strings themselves. If I had used a different fmt print command with a "\n" at the end of each s1 iteration, I'd have seen that. Thank you, Jan! -- 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.
