News for hackers. Stuff that matters.
Re:A Modern JavaScript Tutorial by earthboundkid on Monday December 07, 2020 @02:59PM (#25336529)
That strikes me as perfectly readable. t for template, b for bytes, and s for string. What else would you call them?
Re:A Modern JavaScript Tutorial by yarosv on Monday December 07, 2020 @03:40PM (#25337181)
Sure, what bothers me is how inconsistent it is. Function parameter of type Template is `t` but local variable of type Template is `tmpl`.
Re:A Modern JavaScript Tutorial by earthboundkid on Monday December 07, 2020 @10:02PM (#25341194)
Yes, I would have named the other one returnTmpl or something.
Re:A Modern JavaScript Tutorial by speedgoose on Monday December 07, 2020 @03:30PM (#25337016)
template, bytes, string.
Re:A Modern JavaScript Tutorial by earthboundkid on Monday December 07, 2020 @05:06PM (#25338292)
`bytes` is the name of a stdlib package. `string` is the name of a built in type. `template` is technically available, but only because it’s the name of this package, so it can’t refer to itself.
Re:A Modern JavaScript Tutorial by speedgoose on Tuesday December 08, 2020 @04:39AM (#25343477)
True, but they are all available. The stdlib bytes packages is not loaded, and it's valid to use `string` as a variable name, I just tried.

But even if these names were not available, I don't think using `tpl` or `t` or `b` is what should be preferred.

Re:A Modern JavaScript Tutorial by drran on Monday December 07, 2020 @03:37PM (#25337121)
template, file, text
Re:A Modern JavaScript Tutorial by earthboundkid on Monday December 07, 2020 @05:18PM (#25338450)
Is file a file object? A file path?

All three are “the template”. So, they use polish-ish notation: the template as []byte, template as string, and template as *template.Template.

Re:A Modern JavaScript Tutorial by drran on Monday December 07, 2020 @06:09PM (#25339019)
In just two hours we discovered so much! Let's keep digging.
Re:A Modern JavaScript Tutorial by earthboundkid on Monday December 07, 2020 @10:01PM (#25341180)
I’m not sure I follow. Is two hours a long time or a short time?

I use Go a lot, so I’m used to it’s conventions. b for bytes is obvious to me because I know ReadFile returns bytes (not a file handle or a buffer), but I can see why if you lack context, it can look odd. OTOH, I don’t use Rust, so when I read snippets with 'a lifetimes, they always look “wrong” to me.