I'd suggest a better differentiation between Best and Breadth First Search in the Graphs section.

Acronyms BFS and DFS are used all over the place, but "breadth" and "depth" aren't mentioned anywhere, making it hard for a newcomer to understand what is being referred to.

Right now we can create custom configuration based on presets, however I think it would be worth allowing custom presets also.
This would mean opening up the Preset interface so for example a framework could maintain their own Preset file and users can then use the preset, just by pointing

Since the default output is meant to be human-readable, would it make sense to add thousands separators to make the output more easily readable?

If the rack gem isn't present, the engine emits errors such as:

An error occurred while Rails/HttpStatus cop was inspecting /code/app/controllers/errors_controller.rb:6:4.

See https://github.com/rubocop-hq/rubocop/issues/5745

A PR was opened rubocop-hq/rubocop#5707 but didn't get merged.

global variable 9 detected in same line.
please refer source code
https://github.com/binarymaker/stdclib/blob/develop/source/stdtypes.h

source>ravioli -f -x h .
-------------------------------------------------------------------------------
Globals
-------------------------------------------------------------------------------
stdtypes.h:93 FALSE
stdtypes.h:93 FALSE
stdtypes.h:93 F