Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Problem with bogus conflict between single-arg-String vs CharSequence constructor #667

Closed
cowtowncoder opened this issue Jan 2, 2015 · 0 comments
Closed

Problem with bogus conflict between single-arg-String vs CharSequence constructor #667

cowtowncoder opened this issue Jan 2, 2015 · 0 comments
Milestone
2.5.0

Comments

@cowtowncoder
Copy link
Member

Although it is good idea to allow recognizing CharSequence as almost like an alias for String, this can cause problems for classes like StringBuilder that have separate constructors for both.
This actually throws a bogus exception for 2.5.0, due to introduction of ability to recognize CharSequence.
@cowtowncoder cowtowncoder added this to the 2.5.0 milestone Jan 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.5.0
Development

No branches or pull requests
1 participant
@cowtowncoder