Closed n9wxu closed 1 year ago
All modified lines are covered by tests :white_check_mark:
Comparison is base (
2be332a
) 93.66% compared to head (c873de9
) 93.66%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
/bot run formatting
In general I am confused what the minimal_freertos_example/main.c
file. To me it seems like an objectively worse version of the Posix_GCC/main.c, the WIN32-MSVC-Static-Allocation-Only, the WIN32-MSVC, or the WIN32-MingW main.c files?
/bot run formatting
In general I am confused what the
minimal_freertos_example/main.c
file. To me it seems like an objectively worse version of the Posix_GCC/main.c, the WIN32-MSVC-Static-Allocation-Only, the WIN32-MSVC, or the WIN32-MingW main.c files?
I understand this is a minimal "build" example, than an example demonstrating functionality.
In general I am confused what the
minimal_freertos_example/main.c
file. To me it seems like an objectively worse version of the Posix_GCC/main.c, the WIN32-MSVC-Static-Allocation-Only, the WIN32-MSVC, or the WIN32-MingW main.c files?I understand this is a minimal "build" example, than an example demonstrating functionality.
But if it's a "minimal build example" it should be called that, or contain that information.
This file directly states:
/* This is a simple main that will start freertos and run a periodic task */
In my opinion, if the only reason this file exists is for static analysis it should probably just live in .github
directory. If it's meant to be a true sample main.c file it should have info that would help a new user use it and turn it into an actual main.c
file
/bot run formatting
/bot run formatting
Kudos, SonarCloud Quality Gate passed!
Description
minimal build example
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.