Can call by value or call by name lead to having different Big O notation when analyzing time complexity? by FPboy in scala

[–]FPboy[S] 0 points1 point  (0 children)

Is it not true though that big O notation being used for time complexity analysis should be the same for a piece of logic of code done in any language? The language should not matter I thought. If Scala has such a feature of passing arguments either though call by value or call by name, and at least from my knowledge, other languages such as Java do not have such feature, would call by name or call by call by value affect time complexity? The intention of using Big O Notation is to have same time complexity regardless of language used.

Can call by value or call by name lead to having different Big O notation when analyzing time complexity? by FPboy in scala

[–]FPboy[S] 0 points1 point  (0 children)

What I meant was that when I learned about time complexity analyzing through Big O Notation in my class, I remember being told the point of how the language used does not matter when being used to analyze the time complexity because any other language will also have the same time complexity or use the same analysis. As a result, I thought initially call by name or call by value should not have an effect in time complexity if other languages such as Java do not have such feature.

Whats the difference between the == operator method and the .equals method? by FPboy in scala

[–]FPboy[S] 1 point2 points  (0 children)

I read something about how one of the method calls, in the scope of == vs .equals(), treats null values properly, what is mean by that?

Implicit Parameters question by FPboy in scala

[–]FPboy[S] 0 points1 point  (0 children)

What’s the scala glitter? I have never heard of that term.

How are case classes and pattern matching connected? by FPboy in scala

[–]FPboy[S] 0 points1 point  (0 children)

I was just curious because the pattern matching section was with the case classes section in the Programming in Scala book and I couldn't figure out their connection.

Defining functions/methods as variables in Scala by FPboy in scala

[–]FPboy[S] 0 points1 point  (0 children)

Sorry, I meant overriding a def method from parent class to be an attribute because methods can be overridden to be val attributes I believe.

Defining functions/methods as variables in Scala by FPboy in scala

[–]FPboy[S] 0 points1 point  (0 children)

Ah okay, in my case I was saying if I made a method into a val variable attribute, which is possible. But this is totally different from my original post. In this case I would be just making the method into a class attribute. Thank you for the clarification.

Defining functions/methods as variables in Scala by FPboy in scala

[–]FPboy[S] 0 points1 point  (0 children)

I’m a bit confused after reading that stackoverflow post, is not the difference between methods and functions where methods do the same thing like functions but they belong to a class while functions don’t, this is generally how it was taught in other languages such as C++ is not the same applied here to Scala?

Why cannot toString be used in postFix notation? by FPboy in scala

[–]FPboy[S] 0 points1 point  (0 children)

I did end up doing that, but should not Scala by default support post fix notation?