matryer / matryer/testing-in-go
mlog.Parse
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Regarding your talk, if lines are read from a log file (or other persistent source), accepting a []byte instead of a string may be both convenient and much more efficient; if really read from a file, accepting an io.Reader would be the ideal choice, for which strings.NewReader would be an easy way to supply strings, as in:
mlog.Scan(strings.NewReader("3:04PM,INF,message here"))
http://go-talks.appspot.com/github.com/extemporalgenome/gotalks/iter.slide discusses the relative efficiency of various unbounded-stream iteration techniques. TL;DR either callback based or bufio.Scanner style tend to be the ideal implementations.
(P.S. I was the other meetup presenter)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the mlog.Parse and mlog.Scan entry points named in the issue. Compare the proposed []byte and io.Reader inputs, including the strings.NewReader example, before deciding what behavior needs to be specified. Done means the input API choice is resolved and its behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100