Thank you Mr. Carl Schwan for helping me out :)
OMW TO BECOME A REGULAR KDE CONTRIBUTOR :D
Both are used to reduce the number of times a fn is called by an event that fires repeatedly.
Throttle calls the fn at regular intervals
Debounce calls the fn at a particular instant (either the start/end of the event firing)
Both are used to reduce the number of times a fn is called by an event that fires repeatedly.
Throttle calls the fn at regular intervals
Debounce calls the fn at a particular instant (either the start/end of the event firing)
I'll try to daily drive it because i like this project
I'll try to daily drive it because i like this project
error handling > preconditions & invariants and relating invariants with RAII
im so confused right now. Maybe I'll understand it better with time
error handling > preconditions & invariants and relating invariants with RAII
im so confused right now. Maybe I'll understand it better with time
error handling > introduction, exceptions (try catch, RAII)
implemented a basic vector too
error handling > introduction, exceptions (try catch, RAII)
implemented a basic vector too
modularity > function arguments and return values > argument passing, value return (pass by value & reference), return type deduction (auto), suffix vs prefix return type, structured binding
now i'll do some uni assignments before calling it a day lol
modularity > function arguments and return values > argument passing, value return (pass by value & reference), return type deduction (auto), suffix vs prefix return type, structured binding
now i'll do some uni assignments before calling it a day lol
Thank you Mr. Carl Schwan for helping me out :)
OMW TO BECOME A REGULAR KDE CONTRIBUTOR :D
Thank you Mr. Carl Schwan for helping me out :)
OMW TO BECOME A REGULAR KDE CONTRIBUTOR :D
tourofcpp shall be resumed from tomorrow
tourofcpp shall be resumed from tomorrow
modularity > namespaces
most of my time was spent in reading about CMake and compiling KDE's ebook reader.
develop.kde.org/docs/getting...
This article really satisfied my itch. Cmake always felt like this scary alien thing, now everything FINALLY makes SENSE.
modularity > namespaces
most of my time was spent in reading about CMake and compiling KDE's ebook reader.
develop.kde.org/docs/getting...
This article really satisfied my itch. Cmake always felt like this scary alien thing, now everything FINALLY makes SENSE.
- user defined types: revised yesterday's, enums
- modularity: intro, separate compilation (header files, modules)
kinda reminded me of the OOP paradigms I had learnt in Java before. Abstraction in particular with how header files expose an interface.
- user defined types: revised yesterday's, enums
- modularity: intro, separate compilation (header files, modules)
kinda reminded me of the OOP paradigms I had learnt in Java before. Abstraction in particular with how header files expose an interface.
while also forcing yourself to do things that you must do
:)
while also forcing yourself to do things that you must do
:)
revised yesterdays stuff + user defined types: enums
(overshot my 30m window to maybe an hour cus I was having fun)
revised yesterdays stuff + user defined types: enums
(overshot my 30m window to maybe an hour cus I was having fun)
I can make sense out of only half of ts
...
DO NOT PANIC
I can make sense out of only half of ts
...
DO NOT PANIC
what should I be doing
A) 1 h cpp for the day
B) digital logic design backlog
what should I be doing
A) 1 h cpp for the day
B) digital logic design backlog