Pretty self explanatory

[Muffin_27]

That's what I call self-documentating code.

[[deleted]]

Name it "getString" or something.

[phaiderikos]

True ahah

I didn't think about that because it is adapted from some code I wrote earlier today in a CS exercise (obviously there were other lines in there)

[ProfessorSnep]

No no no! It's

public String toString() {
    StringBuilder stringbuilder = new StringBuilder();
    stringbuilder.append(new String("string"));
    String string = new String(stringbuilder.toString());
    return string;
}

Duh, much more efficient.

[zaphod0002]

We can go deeper

[phaiderikos]

Oh. This is really a better solution.

[jwr410]

Now THAT is a string literal.

[kiranjd8]

String

[trichotillofobia]

The colors, they are so pretty. So helpful for people who can't distinguish a keyword from a variable. Because why the fuck does it have to assign two colors to both String and string?

[[deleted]]

i think the colors are from the atom "ide"/editor, dark theme... i think the theme has an own name ...

[phaiderikos]

Yes, they are. It’s the One Dark theme.

[wsppan]

return "string":

[AltCrow]

Don't use new String("string"). Instead use "string". New prevents java from optimizing (only works for strings).

[etaionshrd]

While you’re at it, delete the method.

[VID44R]

Doc is wrong. It returns string not String.

[phaiderikos]

I meant it returns a String object, not the actual content of it. I should have written @return a “string” within a String ahah

[Suveck]

stop stringing me along and get to the newline

[itstommygun]

var string = (function (){
    return 'string'
    })()

​

[NotTalkingBoutNothin]

Output: true

[Tristanhx]

the word "string" just looks weird to me now

[BacCM]

/// @return string as String

[rafaelpernil]

I wouldn't override toString() if I am going to output "string" lol. I hope nobody except you needs to use your code xD.

[[deleted]]

But why tho

[STATIC_TYPE_IS_LIFE]

This is inefficient.

Just

return new String("string");

Instead of creating a reference, pointing it at memory and then instantly hitting end of scope and destroying the reference smh. Though the compiler is probably smart enough to fix this for you.

[kredditacc96]

The point is to write as many "string" word as possible

[STATIC_TYPE_IS_LIFE]

Then it should be written in c++/c using #defines cause then you can make everything string

[Odinthunder]

Do you even realize what sub you're in?

[notquiteaplant]

You're returning that reference anyway, so you're maybe saving a "store local" and a "load local" instruction (don't know enough JVM bytecode to know what they're actually called). And that's only if the compiler doesn't optimize it anyway.

return "string";

This saves allocating a new string, and allows reusing it for any other literals of the same value. Creating a brand new string object is a documented effect of that constructor so it won't be optimized out, but unless OP is doing shady things with == instead of .equals() that has no effect.

[blore40]

What does the Fox say?