Skip to content

Consider generics in LambdaSafe #17597

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
Closed
philwebb opened this issue Jul 21, 2019 · 1 comment
Closed

Consider generics in LambdaSafe #17597

philwebb opened this issue Jul 21, 2019 · 1 comment
Assignees
@philwebb
Labels
status: invalid An issue that we don't feel is valid

Comments

@philwebb
Copy link
Member

We might be able to apply a similar technique to spring-projects/spring-framework#23178 in our own Lambda checking code.
@philwebb philwebb added the type: task A general task label Jul 21, 2019
@philwebb philwebb added this to the 2.2.x milestone Jul 21, 2019
@philwebb philwebb self-assigned this Sep 20, 2019
@philwebb
Copy link
Member Author

We can't. Unlike the framework we only have access to bean instances, not the definitions. Luckily we don't use LambdaSafe much outside of bean initialization.

@philwebb philwebb added status: invalid An issue that we don't feel is valid and removed type: task A general task labels Sep 27, 2019
@philwebb philwebb removed this from the 2.2.x milestone Sep 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@philwebb philwebb

Labels
status: invalid An issue that we don't feel is valid
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@philwebb