The point object p changed because it calls translate. Note the difference between translate() that moves the point (in 2-D Cartesian coordinate system) and translated() which only creates a translated version. The following example illustrates the concept. If possible, provide a pair of those methods.

What kind of naming convention shall we follow?Ī convention I’m familiar with (from my past time involvement with Qt) is by choosing the right form of the verb: present to indicate a possibly modifying action and past participle to return a new version without mutating the object. Ideally, the user of your module should not always read the documentation to figure out which one they really want. When you build your own module, it is important to choose an API which minimizes this slice vs splice confusion. This is not supposed to be a surprise, after all the name splice implies it. On top of that, splice also mutates the array that calls it. slice ( 1, 2 ) Īlthough splice also takes two arguments (at minimum), the meaning is very different. As you can see, x keeps its elements and y gets the sliced version thereof. The following code fragment illustrates the behavior.

slice ( 1, 2 ) // Īn important aspect of slice is that it does not change the array which invokes it. It’s not very difficult to understand what slice does: 'abc'. It will return a new array containing the elements from the given start index up the one right before the specified end index. According to the specification, slice needs to accept two arguments, start and end. In practice, such a confusion can be avoided by choosing an API that telegraphs the const-correctness of the function.Īrray’s slice is quite similar to String’s slice. These two functions, although they have similar names, are doing two completely different things. In JavaScript, mistaking slice for splice (or vice versa) is a common mistake among rookies and even experts.

Slice splice javascript