Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Added _394.java #31

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

Merged
fishercoder1534 merged 1 commit into fishercoder1534:master from varunu28:master
Jan 11, 2019
Merged

Added _394.java #31

fishercoder1534 merged 1 commit into fishercoder1534:master from varunu28:master
Jan 11, 2019

Conversation

Copy link
Contributor

@varunu28 varunu28 commented Jan 8, 2019

  • Added code with description
  • Added test case
  • Updated README

Copy link
Owner

Left some comments, LGTM otherwise, thanks!

Copy link
Contributor Author

varunu28 commented Jan 8, 2019

@fishercoder1534 I am unable to view your comments on the PR and it is showing me no reviews against the PR also. I was facing this issue during my last PR too. Not sure if Github changed something.

Copy link
Contributor Author

@fishercoder1534 Were you able to check on this?

Copy link
Owner

Yes, I looked into it a bit, I was able to clearly view everything.
But when I switched into incognito mode, I don't see the comments, so I suspect it's due to permission issue, and I didn't really see how Github provides a way around this or setting on this repo that I could adjust.

Copy link
Owner

@fishercoder1534 fishercoder1534 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you able to view comments this way? @varunu28


public class _394 {

public static class Solution {
Copy link
Owner

@fishercoder1534 fishercoder1534 Jan 8, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Solution -> Solution1 that's our convention to allow multiple solutions for one problem. Thanks!

Copy link
Contributor Author

@varunu28 varunu28 Jan 10, 2019
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does a solution exist for this solution in the repo?

Copy link
Owner

@fishercoder1534 fishercoder1534 Jan 10, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it's unique. It's not a namespace conflict thing, we usually start with Solution1, although there might be the only solution for that problem at the moment.
If you could stick to this convention, that'd be great.

Copy link
Contributor Author

@varunu28 varunu28 Jan 11, 2019
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds great. Will make the changes


count.push(Integer.parseInt(s.substring(start, idx + 1)));
}
else if (s.charAt(idx) == '[') {
Copy link
Owner

@fishercoder1534 fishercoder1534 Jan 8, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: move else if line to right behind }, otherwise build will fail like last time. see this commit and this.

else if (s.charAt(idx) == '[') {
str.push("");
}
else if (s.charAt(idx) == ']') {
Copy link
Owner

@fishercoder1534 fishercoder1534 Jan 8, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here.


str.push(str.pop() + sb.toString());
}
else {
Copy link
Owner

@fishercoder1534 fishercoder1534 Jan 8, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ditto.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Owner

Looks like so, I think the problem was: I needed to use "Request Changes" and then click "Submit" instead of just commenting on the code. Lessons learned, fun!

varunu28 reacted with thumbs up emoji

Added _394.java
@fishercoder1534 fishercoder1534 merged commit d35b3b7 into fishercoder1534:master Jan 11, 2019
Copy link
Owner

Copy link
Owner

All right, I fixed it, please run your tests before you submit next time.

fishercoder1534 pushed a commit that referenced this pull request Jun 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fishercoder1534 fishercoder1534 fishercoder1534 approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /