levymatan / geeks4geeks

Collect solutions for Geeks4Geeks Problem of the Day coding questions. https://levymatan.github.io/Geeks4Geeks/

• 👋 Hi, I’m @LevyMatan
• 👀 I’m interested in Embedded systems and Robotics.
• 🌱 I’m currently learning cMake to enable me a more modern build system techniques
• 💞️ I’m looking to collaborate on DIY projects which involves some mechanic componenets.
• 📫 How to reach me ... Here is a great way!

geeks4geeks's Issues

Add semantic versioning to CI

Add auto tags increments according to Semantic Versioning.

fix() --> increase VERSION.PATCH
feat() --> increase VERSION.MINOR
if commit message has: BREAKING-CHANGES in them: Increase VERSION.MAJOR

Also update the project's version

Logger: Add select/deselect all - for each filter catagory

Logger: Add text filter

Update project readme file

Add a solution link to the correct file

Logger: Add more highligher element boxes

Logger: [Style] change default colors to be more pleasant (less intense colors)

Time Complexity Analysis Library

Create a template library for time complexity analysis.
Should be a decorator like that take a function pointer, a parameter generation function,
Call the function N iteration with different parameter input length.
Summarize the performance against theoretical time complexity
Generate a log with plots

Logger: Add find functionality using a keyboard shortcut

add: Count the Number of Full Binary Trees

Add solution + docs+ tests

Logger: Sort the filters checkboxes from a to z

Update cache action to v3

Version 2 used npm 12 which is about to be deprecated

Add a solution link to the correct file in radme

Create a debug utility header

Debug Utilities

Lets distinguish three cases of debug logs:

• Development Debug: This is the most verbose debug log level. In development phase we usually want as much information as possible to follow. The informative logs should enable the developer follow the execution flow of the program with ease.
• Maintenance Debug Mode: After a module/function is developed and tested, sometime there is a need to change/add/modify a dependency or change the code to allow new features. CI will run all tests made available by the developer, if a test fails, we would like to have some information to understand what is going on and help solve the bug.
• Release Runtime Mode: Here we want to keep the debug information to the minimum. The debug information has its cost of memory and CPU clocks consumption, we would like to reduce it to be minimal.

Design Proposal

An header macros library with the three above level controlled by a preprocessor defines.
Development Debug we require build type to be Debug and define of an extra parameter
For example: cmake --build build --target all -D__DEV_DEBUG_ON__
Maintenance Debug Mode will be on in Debug mode.
Release Runtime Mode Will be without any debug info.

Debug Information

The debug information can be: Function start and End, function arguments values.
Flow indications in the programs.
Example:

void main()
{
    DEBUG_PRINT_FUNCTION_START()
    int x;
    printf("Dear user, please enter a number\n");
    scanf("%d", &x);

    if(x > GREEDY_THRESHOLD)
    {
        DEBUG_PRINT("Greedy user flow");
        greedy_user_function()
    }
    else
    {
        normal_flow()
    }
    DEBUG_PRINT_FUNCTION_END()
}

Embedded World

In the embedded business there is a need for neat debug mechanism.
Normally long and high bandwidth requiring logs are an issue.
We would like to be able to control the debug information without a huge impact on:

• Memory consumption
• Runtime execution performance
• Correctability - need to have a separate (sometime it is duplicate) set of variables, never count on debug variable for program flow.

A great bonus is to be able to adjust the debug log levels at runtime!