On Wednesday, September 5, 2018 at 10:38:16 AM UTC-4, Jan Mercl wrote: > > On Wed, Sep 5, 2018 at 4:23 PM Eric Raymond <e...@thyrsus.com > <javascript:>> wrote: > > > Matters in my case because the deserialization of a repository history > can contain hundreds of thousands of constants like "M", "D", "R", and "C" > > representing fast-export stream file operation types. I could intern > them explicitly but it avoid code clutter and some lookup time if I don't > have to. > > Maybe I'm misunderstanding something, but the above quoted seems to talk > about string values obtained at runtime. The linker coalescing string > literals (compile time constants) discussed before does and cannot apply to > string values not known at compile time. >
No, these are actually compile-time constants used in constructor functions that stuff them into instance structures. In C they'd be #define macros. -- 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.
