[Invidam] Week 02 Solution #GoLang #60
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sounmind
reviewed
May 10, 2024
SamTheKorean
approved these changes
May 10, 2024
dev-jonghoonpark
approved these changes
May 10, 2024
| (n = list's size) | ||
| # Code | ||
| ``` | ||
| const visited = -10001 |
There was a problem hiding this comment.
input 값 범위를 사용해서 푸신게 재밌는 접근인것 같습니다 👍
| # Code | ||
| ``` | ||
| func mergeTwoListsV1(list1 *ListNode, list2 *ListNode) *ListNode { | ||
| if list1 == nil && list2 == nil { |
There was a problem hiding this comment.
코드 부분이 인덴트가 4칸일 때가 있고 8칸일때가 있어서 통일해주면 좋지 않을까 싶네요...!
(찾아보니깐 4칸이 권장인것 같네요.)
| ``` | ||
|
|
||
|
|
||
| type Stack[T any] struct { |
There was a problem hiding this comment.
Go는 기본적으로 Stack 과 같은 자료구조를 제공해주지 않나보군요...?!
There was a problem hiding this comment.
넵 ㅠ 다른 풀이들을 보면 별도 자료구조를 구현하지 않고 배열과 내장함수들만 이용하는 경우도 있더라구요.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
2주차 풀이입니다!
1주차와 달라진 점
Important
문제 풀이와 설명 모두 하나의 파일에 올렸어요!
원래는 코드를 올려야 한다고 생각해
.go를 고집했는데, 패키지나 메인함수가 없어 실행할 수 없는 코드를 올리는 게 큰 의미가 없는 것 같아 문서를 올렸어요.4번째 문제를 풀 때, 릿코드의 문서화 기능을 발견하여 이전 문제들과는 퀄리티가 좀 다릅니다..ㅠ
2주차 후기
md문법도 많이 배우네요~