gaborkaszab commented on PR #8:
URL: https://github.com/apache/iceberg-cpp/pull/8#issuecomment-2545642065

   > There is an old stackoverflow question which I think we can take a look
   There is a stackoverflow for everything and for the opposite too. I just 
googled for "Status codes vs exceptions" and it gives me the first 5 results 
supporting exceptions over status codes, I guess because the algorithm is 
biased by my personal preference it learned from me.
   
   > when you set a breakpoint on the method chain and exception happens, how 
do you know which call give out the exception?
   This works well in Java, I don't think it would be any different in C++ 
world. If you get an exception I guess you can check the trace where it was 
thrown and then set your debugger accordingly.
   Also method chaining doesn't mean that you write everything in a single 
line, you could break as you want.
   
   I did a quick run through on this PR and my general opinion is this: This PR 
assumes that we simply want to pull in auxiliary stuff from the Arrow project 
and without questioning whether we'd need them here or not we just pull entire 
files into this project. This is pretty difficult to review TBH, and if someone 
is not from the Arrow project it's even more difficult because they have to 
figure out the initial motivation of each functionality of another project.
   
   I think this should be the other way around. Let's identify some 
functionality that we'd like to develop in this project, like interface for 
catalogs let's say, and if we find something in other projects that could help 
then pull in only the required part. Or let's have a very simple implementation 
ourselves, we can still evolve it later on.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org

Reply via email to