Facebook Go Libraries

#1

Post by akavel » Thu, Nov 13, 2014, 1:51 PM UTC

Facebook Go Libraries
github.com

Re: Facebook Go Libraries

#2

Post by Kiro » Thu, Nov 13, 2014, 2:06 PM UTC

OT but I think GitHub should show tabs as 4 columns. I find Go code is hard to read with all this whitespace.

Re: Facebook Go Libraries

#3

Post by nahname » Thu, Nov 13, 2014, 2:13 PM UTC

Looks more like Naitik Shah's open-source libraries.

Re: Facebook Go Libraries

#4

Post by tuxone » Thu, Nov 13, 2014, 2:19 PM UTC

Kiro wrote: post #2

OT but I think GitHub should show tabs as 4 columns. I find Go code is hard to read with all this whitespace.

Or better, we should save source code files replacing tabs with spaces. That's the best practice that makes everybody happy.

Re: Facebook Go Libraries

#5

Post by custardcream » Thu, Nov 13, 2014, 2:20 PM UTC

tuxone wrote: post #4

Kiro wrote: post #2

OT but I think GitHub should show tabs as 4 columns. I find Go code is hard to read with all this whitespace.

Or better, we should save source code files replacing tabs with spaces. That's the best practice that makes everybody happy.

Go uses tabs. That's the law. It's in the documentation.

Groups of spaces and tabs are semantically different. Tabs mean indentation. Spaces mean spaces.

Re: Facebook Go Libraries

#6

Post by boomlinde » Thu, Nov 13, 2014, 2:25 PM UTC

Kiro wrote: post #2

OT but I think GitHub should show tabs as 4 columns. I find Go code is hard to read with all this whitespace.

No, it should show it as tabs, because that's what it is. Ideally, it should show it as 8 column tabs, as that is what gofmt assumes by default.

Re: Facebook Go Libraries

#7

Post by tuxone » Thu, Nov 13, 2014, 2:25 PM UTC

custardcream wrote: post #5

tuxone wrote: post #4

Earlier quoted context omitted.

Or better, we should save source code files replacing tabs with spaces. That's the best practice that makes everybody happy.

Go uses tabs. That's the law. It's in the documentation. Groups of spaces and tabs are semantically different. Tabs mean indentation. Spaces mean spaces.

My apologies, thank you for the clarification.

Re: Facebook Go Libraries

#8

Post by treehau5 » Thu, Nov 13, 2014, 2:30 PM UTC

custardcream wrote: post #5

tuxone wrote: post #4

Earlier quoted context omitted.

Or better, we should save source code files replacing tabs with spaces. That's the best practice that makes everybody happy.

Go uses tabs. That's the law. It's in the documentation. Groups of spaces and tabs are semantically different. Tabs mean indentation. Spaces mean spaces.

>Tabs mean indentation.

Sorry but this is false. The only thing a tab means, is tab.

Please provide your reasoning for the down voting. Thank you.

Re: Facebook Go Libraries

#9

Post by akavel » Thu, Nov 13, 2014, 2:34 PM UTC

nahname wrote: post #3

Looks more like Naitik Shah's open-source libraries.

He seems the main committer there, indeed... but "Naitik Shah's open-source libraries" seem to be present already at: https://github.com/daaku?tab=repositories ... so what is the "facebookgo" thing then?

edit: the files have "Copyright Facebook, Inc." anyway

Re: Facebook Go Libraries

#10

Post by Kiro » Thu, Nov 13, 2014, 2:44 PM UTC

boomlinde wrote: post #6

Kiro wrote: post #2

OT but I think GitHub should show tabs as 4 columns. I find Go code is hard to read with all this whitespace.

No, it should show it as tabs, because that's what it is. Ideally, it should show it as 8 column tabs, as that is what gofmt assumes by default.

Sorry, changed "spaces" to "columns".