davisp opened a new pull request, #1581:
URL: https://github.com/apache/datafusion-sqlparser-rs/pull/1581

   I mostly did this as an exercise to get a general feel of how the Parser 
implementation is organized. The basics here are that for every top level 
keyword in Parser::parse_statement I created a new module and moved the 
corresponding function to that module. Then I spent a few hours checking `find 
references` and any method that was in a single new module got moved there.
   
   Towards the end I started making some arbitary decisions on where functions 
referenced from multiple modules lived. Some of these seemed obvious, while 
some were certainly arbitrary.
   
   Most of the motivation here was that working on a 13,000 line file was 
causing my editor to be very not happy. After this happy, the largest module is 
now src/parser/select.rs which clocks in at 2142 lines.
   
   I should note, that the only visible changes are hopefully a few functions 
that had visibility flipped from private to public because I forgot about 
pub(crate) when I first started. Other than that, this is purely copy/paste 
moving of code to new module files.


-- 
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: github-unsubscr...@datafusion.apache.org

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


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

Reply via email to