this post was submitted on 27 Dec 2023
94 points (93.5% liked)

Programming

17024 readers
89 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
 

Both zig and go use the dot operator, but I find the '::' operator much more readable.

Vec::new();

Makes it clear that were accessing a static method belonging to the Vec struct/namespace.

Vec.new()

Makes it seem like Vec is an object with a 'new' method.

Am I alone in thinking this?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 7 points 8 months ago (5 children)

I don't agree. Many languages differentiate in terms of standards. In Java, your objects start lowercase, so if you see uppercase, its a static call.

:: looks nice, I guess, but many languages and standards improve clarity of code.

[–] [email protected] 21 points 8 months ago

in java ovjects start lowercase

by convention only though

[–] [email protected] 18 points 8 months ago (2 children)

That's just convention.

:: is enforced by the compiler.

[–] [email protected] 6 points 8 months ago

Yeah, but does that matter? I don't think, I've ever accidentally broken these conventions, where compiler assistance would have been helpful.

[–] [email protected] 8 points 8 months ago (1 children)

Also: :: in Java is method reference. In Kotlin it's reflection.

I'd say if you care a lot about distinguishing contexts it's really the job of the IDE to highlight syntax.

Don't write code as though you're going to read it in plain text imo.

[–] [email protected] 6 points 8 months ago

I like how Java uses it. As a C# dev I wish for it sometimes.

[–] [email protected] 3 points 8 months ago

Yeah, kind of curious what Go does here then / what the actual experience is like.
It abuses casing for public/private, so presumably there's no way to see whether a given sequence of letters is a variable or a type.

[–] [email protected] 2 points 8 months ago* (last edited 8 months ago)

In Java, your objects start lowercase, so if you see uppercase, its a static call.

Not really, that's just the way a specific coding style was specified. You're free to refactor all your projects to follow any other coding style if you really want to, and your programs will continue to work just fine.