Timeline for Pros and cons of semantically-significant capitalization
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 13, 2023 at 20:49 | comment | added | James | I think I was misreading "ignore it" as the IDE hiding the accessibility modifier words from you. | |
| Jul 13, 2023 at 19:46 | comment | added | feldentm | @James most languages use ordinary keywords for this purpose and all IDEs I've seen in the last two decades had special colors for at least the entire keyword group. Am I missing something here? | |
| Jul 13, 2023 at 18:13 | comment | added | James | "For most languages, there is syntax highlighting which allows you to colorize the visibility definition and ignore it, if you don't care." I have seen color highlights, but never what you are describing. What language and editor combo has this? | |
| Jul 13, 2023 at 9:35 | comment | added | Passer By | I have no experience in Go code generators, but having the API and implementation in the same package is pretty much intended isn't it? | |
| Jul 13, 2023 at 9:21 | comment | added | feldentm | If a struct in your API has a field, that field is either public or your implementation is in the API package. Having API and implementation in the same package is uncommon in all languages and doesn't play well with code generators often used in Go. A solution is to restrict visibility to a group of packages like private[package] in Scala. Java modules also provide a solution that is more complex as they had to add it at a later point. | |
| Jul 13, 2023 at 8:26 | comment | added | Passer By | What do you mean by "you can't share definitions between an API and an implementation package"? What isn't shared? Why do you have two packages? What hypothetically solves your problem? | |
| Jul 13, 2023 at 7:13 | history | answered | feldentm | CC BY-SA 4.0 |