this post was submitted on 13 Sep 2026
40 points (100.0% liked)

Programming

28458 readers
271 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 !webdev@programming.dev

founded 3 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
40
What is your preferred import style (sh.itjust.works)
submitted 1 day ago by programmerlexi@sh.itjust.works to c/programming@programming.dev
39 comments fedilink hide all child comments
 

There are a few I'm aware of:

  1. Rust-style use (multiple imports per statement, renaming items using as)
  2. Java-style import (single import per statement, no renaming (afaik))
  3. Zig-style let xlib = @import("xlib") (imports as assignments)
  4. C-style #include (no importing, just pastes the code of the named file)
you are viewing a single comment's thread
view the rest of the comments
[–] Traister101@lemmy.today 1 points 4 hours ago* (last edited 4 hours ago)

Java doesnt have value types or structs. You have primatives (booleans, integer types and float/double) and then everything else (even the uppercase primative types like Boolean) are reference types, IE on the heap. For stuff that plays with pointers you generally just call into native code, get back a long (the pointer to whatever you just allocated) and you call into native code to do stuff with the pointer. Native code can make a proper java object but it's involved and has all the same cons as allocating one in Java land.

Supposedly records (a pseudo struct) might get stronger optimization options (IE put on the stack) but fundementaly reference types are just pointers and if you get an object via constructor or parameter the language must support you putting it in global state