Name | Link | Description |
---|---|---|
128 Nops | https://128nops.com/ | A blog focusing on low-level programming, reverse engineering, and performance optimization. |
ACM Queue - Articles | https://queue.acm.org/ | A public |
Discover gists
// Project | |
plugins { | |
alias(libs.plugins.ksp) apply false | |
alias(libs.plugins.hilt) apply false | |
} | |
// Module | |
plugins { | |
alias(libs.plugins.ksp) | |
alias(libs.plugins.hilt) |
To setup debugging for Odin programs on Windows with VsCode follow these steps:
- make sure you have the C/C++ extension pack (VsCode extension) installed
- create a
.vscode
folder at the root of your Odin project - copy the
launch.json
andtasks.json
into it - click on the debug tab in VsCode, then click on the debug button at the top (or press F5)
Note: if you want to use a starter template which also sets up a tracking allocator which tracks and reports memory leaks you can use: https://github.com/RednibCoding/Odin-Starter
Organizing your Go (Golang) project's folder structure can help improve code readability, maintainability, and scalability. While there is no one-size-fits-all structure, here's a common folder structure for a Go project:
project-root/
├── cmd/
│ ├── your-app-name/
│ │ ├── main.go # Application entry point
│ │ └── ... # Other application-specific files
国内从 Docker Hub 拉取镜像有时会遇到困难,此时可以配置镜像加速器。
Dockerized 实践 https://github.com/y0ngb1n/dockerized
You are an assistant that engages in extremely thorough, self-questioning reasoning. Your approach mirrors human stream-of-consciousness thinking, characterized by continuous exploration, self-doubt, and iterative analysis. | |
## Core Principles | |
1. EXPLORATION OVER CONCLUSION | |
- Never rush to conclusions | |
- Keep exploring until a solution emerges naturally from the evidence | |
- If uncertain, continue reasoning indefinitely | |
- Question every assumption and inference |
People
:bowtie: |
😄 :smile: |
😆 :laughing: |
---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
Answer: All APIs of Node.js library are aynchronous that is non-blocking. It essentially means a Node.js based server never waits for a API to return data. Server moves to next API after calling it and a notification mechanism of Events of Node.js helps server to get response from the previous API call.
Source: tutorialspoint.com
// Room.cpp | |
void ARoom::SetupDefaultObject(UBlueprintGeneratedClass* BlueprintClass) | |
{ | |
checkf(HasAnyFlags(RF_ClassDefaultObject), TEXT("ARoom::SetupDefaultObject() can only be called on ARoom default objects.")); | |
checkf(BlueprintClass, TEXT("Cannot setup default room object with null blueprint class.")); | |
if (bIsDefaultSetup) return; | |
TArray<const UBlueprintGeneratedClass*> BlueprintClasses; | |
UBlueprintGeneratedClass::GetGeneratedClassesHierarchy(BlueprintClass, BlueprintClasses); | |
for (const UBlueprintGeneratedClass* Class : BlueprintClasses) |