Quick Reminder: Java Primitive Types Sizes

Quick Reminder:


 

Java's primitive types and their sizes :

Data Type Size
char 2 bytes (16 bits)
short 2 bytes (16 bits)
int 4 bytes (32 bits)
float 4 bytes (32 bits)
long 8 bytes (64 bits)
double 8 bytes (64 bits)

Commentaires

Enregistrer un commentaire

Posts les plus consultés de ce blog

Restoring the Local Changes Tab in IntelliJ IDEA (2024)

Image
Restoring the Local Changes Tab in IntelliJ IDEA (2024) Local change tab not showing up in last version of IntelliJ (2024) :  In the latest version of IntelliJ IDEA(2024), the Local Changes and Shelf features have been moved to a separate Commit tool window on the left. If you prefer the old behavior and layout, follow these steps:     Open IntelliJ IDEA.     Go to Version Control in the settings.     Under the Commit section, uncheck the option for “ Use non-modal commit interface ” The familiar Local Changes tab will now appear inside the Git tool window. That’s it! You’ll have the Local Changes tab back as before. Enjoy 😊
Lire la suite

Copilot Blank Chat in IntelliJ? Create the Missing Files to Fix It

Image
        Unhandled exception ...  com.github.copilot.platform.utils.VirtualFileNotFoundException : Cannot find virtual file for URL: file:///C:/...   If Copilot Chat is blank in IntelliJ and you see VirtualFileNotFoundException with Cannot find virtual file for URL, Copilot is referencing a deleted file. Recreate the file (even empty), sync/restart, done.  Why it happens Copilot keeps a reference to a file you deleted or moved. IntelliJ’s VFS can’t resolve it → the chat UI crashes. The fast fix (what worked for me) Recreate the exact folder path shown in the error. Create the missing file (an empty Java class with minimal valid code is fine). (For example, in my case I created the Java file and added a valid class with minimal content inside it.) If you don't write a valid class, you will get another error, so make sure to add at least the basic structure inside the file. Restart IntelliJ (Ctrl+Alt+Y or File → Invalidate Caches / Restart). (In my cas...
Lire la suite

Resolving Concurrency Conflicts in Java REST APIs: A Case of 412 Precondition Failed

Image
  Resolving Concurrency Conflicts in Java REST APIs: A Case of 412 Precondition Failed   While developing a Java REST API, we encountered a perplexing issue: two deployed endpoints were returning unexpected results. The first endpoint called operated correctly, while the second returned a 412 Precondition Failed error . This behavior was consistent regardless of the calling order of the endpoints. Upon investigation, we discovered that the issue was related to concurrency management and the ETags returned by our API. By refining the entity version comparison logic, focusing on specific attributes such as the ID or other relevant fields, we resolved this conflict and ensured the smooth operation of our endpoints. While this was the solution to our particular issue, it’s important to remember that similar symptoms can stem from different underlying problems. However, if you’re facing a similar challenge, it’s worth taking a closer look at the concurrency m...
Lire la suite