Skip to content
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.

Add a note on overloads behavior #41

Open
abreslav opened this issue Jul 13, 2017 · 1 comment
Open

Add a note on overloads behavior #41

abreslav opened this issue Jul 13, 2017 · 1 comment

Comments

@abreslav
Copy link

In the process of language evolution, subtle changes may happen to overload resolution algorithms, so it's advisable to design one's overloads so that they all "do the same thing", and the change in behavior is not so huge if a different overload is chosen by the compiler.

@yole
Copy link
Contributor

yole commented Dec 21, 2017

This is quite a vague recommendation. Can you provide an example of a set of overloads that doesn't follow this recommendation, and how it can be changed to start following it?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants