Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
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
Fix names of overloaded methods with ref type parameters #139
Fix names of overloaded methods with ref type parameters #139
Changes from 1 commit
7f2cc78
dd40ed1
00605c1
7038a1a
60eba62
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I need to take a closer look and will appreciate some READMEs about the apporach taken with these tasty files, that's quite interesting.
I also checked that this function is backwards compatible on the https://github.com/Glavo/gjavah project tests.
But we still need to ensure sbt-tests of this project are running.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not clear on what you are getting at with your mention of READMEs. Did that line belong to the previous comment?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean that if we want to keep these tasty files in the repository we need a direct description of what they are, how to use them to debug, etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All this stuff is gone. You can just compile the source in the test code to see it now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens in case
java.home
for some unpredictable reason is empty?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't know the answer to that question. I know it did not work on my laptop without providing a java home. The CMake find JNI functionality was lost without it. I think the real solution is to allow this plugin to be configurable to run as is (no JAVA_HOME set), as I modified it, or with a user-specified JAVA_HOME. That should be another PR. I just did enough to get things to work on my laptop.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My comment was that doing
.get
is unsafe. We can append it to the list of params in case it's present, why not.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is modified in the update. Is there a way to make it cleaner?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this does not belong to the resources folder as well as all the related tasty files. But we cat still keep tasty files in a separate folder i.e. in the plugin sbt-test directory in a new directory with a full
sample-overloaded
project; similar to what we already have.And we'd need a README to those tasty files and how to deal with them / why we need them.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we add a full test, similar to others for this proxy along with its JNI component into a separate project into the sbt-test/sbt-jni directory for consistency?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
next update