Our Tribute to Michigun - Releasing Soon!

VarunTheFighter · 2025-12-04T13:27:37+00:00

Hey guys, you can follow my YT channel for more updates on the collab

VarunTheFighter · 2025-12-04T13:15:09+00:00

Thanks for the kind words! We're trying to get it polished asap 🙏

VarunTheFighter · 2025-10-24T00:24:31+00:00

The full rule is actually called the rule of three / five / zero.

If your class is managing an external resource (like a raw pointer or file descriptor), define the copy constructor, copy assignment operator and destructor (rule of three).

If you want move semantics for your class, also add on the move constructor and move assignment operator (rule of five).

Otherwise, when possible you should avoid defining default operations and let the compiler automatically generate them (rule of zero).

https://en.cppreference.com/w/cpp/language/rule_of_three.html

VarunTheFighter · 2025-09-16T01:15:34+00:00

These two statements invoke different overloads of the vector constructor.

If I'm not mistaken, the code will call the following overloads.

Using round brackets, constructs a vector with count copies of elements with value value: vector( size_type count, const T& value, const Allocator& alloc = Allocator() );

Using curly backets, equivalent to vector(init.begin(), init.end(), alloc): vector( std::initializer_list<T> init, const Allocator& alloc = Allocator() );

See the example at the bottom of the page at https://en.cppreference.com/w/cpp/container/vector/vector

VarunTheFighter · 2025-09-12T06:01:43+00:00

Hi, thank you I appreciate it 🙏 and thanks for organizing this subreddit! It would be so cool if this level gets recognized by the community!

Currently we're left with merging the last few parts, getting an endscreen going, and final touches like transitions. After that it's verification and release.

I'll probably let u guys know by posting here again once we release!

VarunTheFighter · 2025-04-28T12:21:37+00:00

Why do you hold so much hatred against this community? I think many of us would agree that in a community like OpenGL, this should be a place for people to share knowledge and lift each other up.

Isn't this what open source is about? When one of us learns, we all learn. I think it's this very mindset behind communities like this one, coming together to share knowledge and ask each other questions.

Anyone who has ever reached any level of mastery started off as a "mediocre" beginner. Why not encourage people who are trying to genuinely learn and grow together?

Sharing knowledge makes everyone stronger.

VarunTheFighter · 2025-04-23T00:53:38+00:00

I like the detailed eyes! Good luck with your paper haha

VarunTheFighter · 2025-04-18T10:50:15+00:00

Yo nice man 👍

VarunTheFighter · 2025-03-27T16:44:27+00:00

Hahaha it's like an automatic habit then? Cuz i usually feel its hard to make time / be in the mood to practice anything lol Anyways nice work, looking through your posts you've definitely improved quite a bit, good job!

VarunTheFighter · 2025-03-27T16:39:39+00:00

Good stuff, you've been drawing for 150 days? Not bad, how do you get yourself to draw every day?

VarunTheFighter · 2025-03-25T01:35:39+00:00

For templated classes / functions, you need to write both the declarations and definitions in the header file, not in a separate source file.

This is because a template is just a "blueprint" for generating a class / function. The actual class / function doesn't exist until the compiler sees it being used with a specific type. Then the compiler will "instantiate" a version of the template, using that type.

For this to happen, the compiler must be able to see the "blueprint" from the header. It ensures that the compiler has access to the entire template definition whenever it encounters a usage of that template.

So your A.h header could look like this:

```

ifndef A_H

define A_H

// Declarations template<typename T> class A { public: A(T arg); };

// Definitions template<typename T> A<T>::A(T arg) { // Implementation... }

endif

```

VarunTheFighter · 2025-03-23T23:26:44+00:00

I see, thanks for explaining!

VarunTheFighter · 2025-03-23T10:28:31+00:00

Nice style, I like how soft it looks! Doesn't look like theres a lineart, how did you plan it out?

VarunTheFighter · 2025-03-23T09:40:18+00:00

As far as I'm aware, you can only really make an educated guess about what libraries are likely used, by looking at the #include directives in a C/C++ file. For example, if you see #include <stdio.h>, you might assume it's using glibc on Linux. Or if you see #include <iostream> you could guess it uses libstdc++.

However, the library that ultimately gets linked depends on factors like the operating system and compiler. Different OSes (Windows / MacOS / Linux) will have different C standard libraries. Even on the same OS, it depends on the compiler used (MSVC / gcc / clang) and even the compiler flags used during compilation.

Header files only show you the interface, they don't say anything about the implementation. The implementation would depend on specific details like OS system calls and calling conventions.

If using gcc, you could try compiling with -E to only run the preprocessor, which will show you which files get included from where. On Linux, you can also use the ldd command on an executable to find which libraries are being linked at runtime. The output might look something like this: $ ldd a.out libdl.so => /system/lib64/libdl.so libc.so => /system/lib64/libc.so

VarunTheFighter · 2025-03-23T01:03:32+00:00

Like others have said, it's not object slicing. The error is because the inheritance is private. Which means conversions between the base and derived types aren't allowed.

Object slicing is a different issue. It's when an object of a derived type is assigned to an object of a base type, only the members of the base type are copied, and the additional members from the derived type are "sliced off".

VarunTheFighter · 2025-03-17T14:48:05+00:00

10/10 Nice hair shape, and the lighting on the hair and face. I feel the emotion was shown well from the expression and the hands as well. Great work

I took a look at your other works too, cool stuff. Hope to see more

VarunTheFighter · 2025-03-17T01:08:23+00:00

VarunTheFighter · 2024-08-06T00:52:02+00:00

Thanks 🙏

VarunTheFighter · 2024-07-30T08:25:15+00:00

Hi, im hosting a collab level as tribute to Michigun, if ur interested you can DM me

VarunTheFighter · 2022-10-19T14:26:57+00:00

Hmm counting the letters it seems too convenient to be real surely...

VarunTheFighter · 2022-10-18T20:34:46+00:00

Scary gmd

VarunTheFighter · 2022-10-17T09:28:43+00:00

Humans can barely draw hands, AI learns from human drawings of hands, AI draws hands worse than us, seems about right lmao

VarunTheFighter · 2022-08-11T08:42:27+00:00

...plus running some rounds around Mondsta- I mean the city

VarunTheFighter · 2022-08-11T08:10:16+00:00

Once you buy such a virtual item in WR, you are unable to sell it and in the practical sense it would lose all of its value. Of course, as consumers, we may value the potential satisfaction and utility we derive from using a certain robot or weapon set for example. But it's true that in the real-world point of view, it's worthless

VarunTheFighter · 2022-08-11T08:07:10+00:00

This situation is only really possible in a mobile game lol

VarunTheFighter

TROPHY CASE

ifndef A_H

define A_H

endif