Skip to content

feat: Add writeTsv function#142

Merged
mchav merged 1 commit intoDataHaskell:mainfrom
Carrotstrip:writeTsv
Feb 16, 2026
Merged

feat: Add writeTsv function#142
mchav merged 1 commit intoDataHaskell:mainfrom
Carrotstrip:writeTsv

Conversation

@Carrotstrip
Copy link
Contributor

I just copied the implementation of writeCsv here, so I don't really understand why there are lazy and non-lazy versions. @mchav could you help me understand this?
Also, I didn't write any tests because there were none for writeCsv, but I did check out the output in the REPL. Would it be worth adding tests for both of these write functions, or maybe just the writeSeparated function that does most of the work? Maybe just a string comparison of manually audited output for some small dataframe?

#119

@daikonradish
Copy link
Contributor

Yes, I think it's a good idea to test writeSeparated. Please write some tests if possible!

@daikonradish
Copy link
Contributor

@mchav - this looks good to go, right?

@mchav
Copy link
Member

mchav commented Feb 16, 2026

I was waiting on final word on the tests. We can proceed without them since it's a straightforward change.

@daikonradish
Copy link
Contributor

i think maybe let's just go with it. seems low risk. i was just trying to peer pressure @Carrotstrip into writing some tests...

@mchav mchav merged commit 1add5cd into DataHaskell:main Feb 16, 2026
7 checks passed
@Carrotstrip
Copy link
Contributor Author

removed the lazy function as discussed with @mchav. Re testing: since dataframe afaiu is sort of a port of a very canonical implementation of the concept of dataframes (pandas), would it make sense to use certain pandas outputs as a golden copy to compare our own outputs to? seems like it could be a useful class of testing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants