🔹 Part2: Exploring type_traits in C++ (is_integral & enable_if) This short video is part of my "C++ Programming Topics" series 👇 And also included in my broader C++ templates playlist. 💡 The problem: When writing generic C++ code, not every type should be treated the same way. This can lead to: -Invalid operations on unsupported types -Hard-to-read template errors -Fragile and unsafe generic code ❌ 📌 This is where the type_traits library becomes essential: 👉 It gives you compile-time tools to inspect and control types. 💡 The solution: Understanding and implementing core utilities like: ✔️ is_integral — detect whether a type is an integral type ✔️ enable_if — conditionally enable/disable functions ✔️ type_traits — the foundation of compile-time type logic ⚙️ Bonus insight from the video: You’ll explore simplified implementations to really understand how they work under the hood: 1️⃣ is_integral How the compiler determines if a type belongs to integral types 2️⃣ enable_if How to include/exclude functions during compilation 3️⃣ Combining both Apply constraints to templates for safer and cleaner code 🎯 Key takeaway: Don’t just use type_traits—understand how they work. That’s what unlocks the real power of modern C++ templates. 🎥 Watch the video: https://lnkd.in/d7zPHDzb 📚 Full playlist: https://lnkd.in/dDNVWvVC #cpp #moderncpp #programming #softwareengineering #templates #metaprogramming #cleancode

🔹 Part 1: C++ Concepts vs SFINAE (Practical Guide) This short video is part of my "C++ Programming Topics" series 👇 And also included in my broader C++ templates playlist. 💡 The problem: SFINAE is powerful—but it often leads to complex, hard-to-read template code. This can cause: -Cryptic compiler errors -Reduced code clarity -Higher learning curve for maintainers ❌ 📌 This is where C++20 Concepts shine: 👉 They provide a clean and expressive way to constrain templates. 💡 What you’ll learn in this video: ⚙️ Step-by-step evolution from SFINAE to Concepts: 1️⃣ Using enable_if in template parameters A cleaner alternative than putting it in the return type 2️⃣ Constraining a template class (Wrapper) Allow only integral types using SFINAE 3️⃣ Generic sum function Handle different types and control the return type 4️⃣ Concepts vs SFINAE Clear comparison in readability and maintainability 5️⃣ Writing your own concept Define a requirement for types that support add and sub 6️⃣ Combining Concepts with type_traits Reuse existing utilities for powerful constraints 🎯 Key takeaway: Concepts don’t replace SFINAE—they simplify it. Use Concepts when readability matters, and SFINAE when you need lower-level control. 🎥 Watch the video: https://lnkd.in/dpiQNQcF 📚 Full playlist: https://lnkd.in/dDNVWvVC #cpp #moderncpp #programming #softwareengineering #templates #concepts #metaprogramming #cleancode

Built a simple C++ Compiler from Scratch! Sharing my latest project - a simple yet functional C++ compiler built from the ground up using Flex, Bison, and ANTLR4. This project dives into the core phases of compilation and helped me strengthen my understanding of how programming languages actually work behind the scenes. Key Features: • Lexical Analysis using Flex • Syntax Parsing using Bison & ANTLR4 • Three Address Code (TAC) Generation • Basic Assembly Code Generation • Detailed logging of each compilation phase How it works: 1. Source code is tokenized into meaningful units 2. Tokens are parsed based on grammar rules 3. Intermediate code (TAC) is generated 4. Final pseudo-assembly code is produced What I learned: Building a compiler from scratch gave me hands-on experience with: • Language design fundamentals • Parsing techniques and grammar rules (Bison & ANTLR4) • Intermediate representations • Low-level code generation concepts 🛠️ Tech Stack: C++ | Flex | Bison | ANTLR4 | Makefile 📌 Example outputs include: ✔ Token logs from lexical analysis ✔ Three Address Code ✔ Assembly-like instructions This project is a small but meaningful step into the world of compilers and systems programming. 🔗 GitHub Repo: https://lnkd.in/ggkcdTyV I’d love to hear your thoughts or suggestions for improvement! #CPlusPlus #CompilerDesign #Flex #Bison #ANTLR4 #SystemsProgramming #SoftwareEngineering #LearningByBuilding #BIE #bioinformatics #BAU

🔹 Type Deduction in C++ (auto, decltype) This short video is part of my "C++ Programming Topics" series 👇 And also included in my broader learning playlist. 💡 The problem: Many developers either over-specify types or rely on guesswork when writing modern C++ code. This can lead to: -Verbose and harder-to-read code -Subtle bugs when types are not what you expect -Reduced flexibility when refactoring ❌ 📌 This is where type deduction becomes powerful: 👉 Let the compiler infer the correct type safely and efficiently. 💡 The solution: Using modern C++ features like auto, decltype, and template deduction: ✔️ Write cleaner and more concise code ✔️ Reduce redundancy ✔️ Let the compiler handle complexity ⚙️ Bonus insight from the video: You’ll see how type deduction works in different scenarios: 1️⃣ auto Great for simplifying variable declarations Improves readability when types are obvious 2️⃣ decltype Useful when you need the exact type of an expression Helps in advanced template and generic programming 3️⃣ Template Type Deduction The core concept behind generic programming Enables flexible and reusable code 🎯 Key takeaway: Don’t fight the compiler—use it. Modern C++ gives you tools to write cleaner, safer, and more maintainable code. 🎥 Watch the video: https://lnkd.in/dZSDe2Pi 📚 Full playlist: https://lnkd.in/dDNVWvVC 📚 Source code, examples, and notes: https://lnkd.in/dy2Kp-4f #cpp #moderncpp #programming #softwareengineering #templates #cleancode

.𝗡𝗲𝘁 𝟭𝟬 - 𝗖# 𝟭𝟰 𝗝𝘂𝘀𝘁 𝗠𝗮𝗱𝗲 𝗣𝗿𝗼𝗽𝗲𝗿𝘁𝗶𝗲𝘀 𝗖𝗹𝗲𝗮𝗻𝗲𝗿 - 𝗳𝗶𝗲𝗹𝗱 𝗸𝗲𝘆𝘄𝗼𝗿𝗱 In older C# code, if we wanted to add logic inside a property, we usually had to create a separate private variable. With C# 14, we can now use the 𝗳𝗶𝗲𝗹𝗱 keyword inside a property accessor. It gives direct access to the compiler generated backing field, so we can keep the code shorter and cleaner. 𝗕𝗲𝗳𝗼𝗿𝗲 public class Student { 𝗽𝗿𝗶𝘃𝗮𝘁𝗲 𝗶𝗻𝘁 _𝗺𝗮𝗿𝗸𝘀; public int Marks { get => _marks; set => _marks = value < 0 ? 0 : value; } } 𝗪𝗶𝘁𝗵 𝗳𝗶𝗲𝗹𝗱 𝗶𝗻 𝗖# 𝟭𝟰 public class Student { public int Marks { get; set => 𝗳𝗶𝗲𝗹𝗱 = value < 0 ? 0 : value; } } 𝗪𝗵𝗮𝘁 𝗰𝗵𝗮𝗻𝗴𝗲𝗱? We no longer need this line: private int _marks; The compiler creates the backing field for us, and field lets us use it directly inside the property accessor. 𝗪𝗵𝘆 𝘁𝗵𝗶𝘀 𝗶𝘀 𝘂𝘀𝗲𝗳𝘂𝗹   • Cleaner code.   • Less boilerplate.   • Same control over validation or simple logic. #dotnet #csharp #softwaredevelopment #dotnetdev #programming

Day 47 Designing Data-Intensive Applications by Martin Kleppmann Chapter 4 Encoding and Evaluation In some programming languages, null is acceptable default for any variable, but in Avro, of you want to allow field to be null, you have to use a union type. Example: union{ null, long, string} field; indicates that field can be a number, or a string, or a null. You can only use null as a default value, of it is one of the branches of Union. Changing the datatype of a field is possible, provided that Avro can convert the type. The reader's schema can contain aliases for field names, so it can match old writer's schema field names against the aliases. Changing a field name is backward compatible, but not forward compatible.

What is Escape Analysis in Go Today I learned about an important concept in the Go programming language called Escape Analysis. Escape Analysis is a process used by the Go compiler to decide where a variable should be stored, either in the stack or in the heap. If a variable is used only inside a function, it stays in the stack and is removed when the function execution is completed. But if a variable is needed outside the function (for example, returning its address), it cannot safely stay in the stack. In that case, the compiler moves it to the heap. This is called “escape to heap”. If a value is returned normally (by value), Go simply copies the value, so no escape happens. In simple terms, Go automatically manages memory by deciding whether a variable should stay in the stack or move to the heap using Escape Analysis.

🔹 C++20 Syntactic Sugar: Concepts vs SFINAE This short video is part of my "C++ Programming Topics" series 👇 And also part of my full playlist. 💡 The problem: Before C++20, constraining templates meant relying on SFINAE (std::enable_if)… Which often leads to: -Complex and unreadable function signatures 😵 -Confusing compiler errors -Code that’s hard to maintain ❌ 📌 This is the limitation of SFINAE: 👉 Powerful, but not developer-friendly. 💡 The solution in C++20: Concepts bring clarity and intent to template constraints. Instead of complicated syntax, you can simply write: ✔️ std::integral auto for clear constraints ✔️ More readable and expressive code ✔️ Much better error messages ⚙️ Bonus insight from the video: You’ll see the evolution step by step: 1️⃣ Generic functions with auto Cleaner type deduction 2️⃣ SFINAE with std::enable_if Works, but verbose and harder to read 3️⃣ Concepts (C++20) Modern approach for clean and maintainable constraints 🎯 Key takeaway: Concepts don’t just replace SFINAE… They make your intent obvious and your code significantly cleaner. 🎥 Watch the video: https://lnkd.in/dvvzwr8Q 📚 Full playlist: https://lnkd.in/dDNVWvVC 📚 Source code, examples, and notes: https://lnkd.in/dy2Kp-4f #cpp #moderncpp #cpp20 #concepts #templates #softwareengineering #cleancode

Built a custom string handling class in C++ from scratch — without using std::string. This project focuses on: • Dynamic memory management using new[] and delete[] • Implementation of the Rule of Three (Destructor, Copy Constructor, Copy Assignment) • Manual string manipulation algorithms (reverse, case conversion, word counting) • Operator overloading for intuitive usage (+, +=, [], (), comparison operators) The goal was to deeply understand how strings work internally rather than relying on built-in abstractions. A great exercise in mastering memory management, object-oriented programming, and low-level string operations in C++. #cpp #programming #softwareengineering #oop #learning #developers

So last week, while I was internally implementing a basic version of the C++ STL vector, I was studying how to make it more efficient and be careful about the memory, in java garbage collection took care of the unreferenced heap memory but in C++, I was thinking how to handle it, and in various explanations, I saw a trick ( a pattern to be precise ), 💡 The idea is simple but elegant: • Tie the lifetime of a resource (memory, file, mutex, etc.) to the lifetime of an object • Acquire the resource in the constructor • Release it automatically in the destructor Its a powerful design principle: RAII (Resource Acquisition Is Initialisation). The destructor is automatically called when an object goes out of scope (during normal execution). This means cleanup is handled deterministically, without relying on the programmer to remember it. For example, if we release allocated memory inside the destructor, we don’t have to worry about leaks. This becomes especially important during exceptions when stack unwinding occurs, destructors are still called, ensuring resources are properly freed. Why RAII is powerful: • Prevents memory leaks • Exception safe by design • Works for all kinds of resources (not just memory) • Forms the backbone of modern C++ (smart pointers, STL containers, etc.) This concept helped me understand and write safe and reliable C++ code. Happy Coding :) #cpp #cplusplus #programming #softwareengineering #systemsprogramming #lowlevelprogramming #codingconcepts