<feed xmlns='http://www.w3.org/2005/Atom'>
<title>eglantine-cirakg/src/common/detached_tasks.cpp, branch nx2</title>
<subtitle>Mirror of github.com/cira0100/Eglantine-public nx2, a fork of Djihads80/Eglantine.</subtitle>
<id>https://git.cirakg.xyz/eglantine-cirakg/atom?h=nx2</id>
<link rel='self' href='https://git.cirakg.xyz/eglantine-cirakg/atom?h=nx2'/>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/'/>
<updated>2026-07-09T01:46:06+00:00</updated>
<entry>
<title>[common] remove DetachedTasks object usage (#4096)</title>
<updated>2026-07-09T01:46:06+00:00</updated>
<author>
<name>lizzie</name>
<email>lizzie@eden-emu.dev</email>
</author>
<published>2026-07-09T01:46:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=c2e74a93804f0ba4e7e87a95e8881bbe817aa0a4'/>
<id>urn:sha1:c2e74a93804f0ba4e7e87a95e8881bbe817aa0a4</id>
<content type='text'>
this was only ever used for announce room json on one single instance

this object is pretty much a danger to society and shouldnt exist, especially since its:
a) a singleton
b) spawns objects out of thin air
c) doesn't respect RAII and can outlive its parent objects (big no no)

generally we shouldnt endorse objects like these in the future, but alas, it existed, now it has to begone
additionally there is a similar object in KWorkerTaskManager but it's not as egregious as this one.
check that this didnt break the usual announce room json logic

Signed-off-by: lizzie &lt;lizzie@eden-emu.dev&gt;

Reviewed-on: https://git.eden-emu.dev/eden-emu/eden/pulls/4096
Reviewed-by: CamilleLaVey &lt;camillelavey99@gmail.com&gt;
Reviewed-by: MaranBr &lt;maranbr@eden-emu.dev&gt;
</content>
</entry>
<entry>
<title>general: Silence -Wshadow{,-uncaptured-local} warnings</title>
<updated>2023-07-18T23:31:35+00:00</updated>
<author>
<name>lat9nq</name>
<email>22451773+lat9nq@users.noreply.github.com</email>
</author>
<published>2023-07-18T23:31:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=30e4e8c2f4db4811315e1101d1e9087f42895781'/>
<id>urn:sha1:30e4e8c2f4db4811315e1101d1e9087f42895781</id>
<content type='text'>
These occur in the latest commits in LLVM Clang.
</content>
</entry>
<entry>
<title>chore: make yuzu REUSE compliant</title>
<updated>2022-07-27T10:53:49+00:00</updated>
<author>
<name>Andrea Pappacoda</name>
<email>andrea@pappacoda.it</email>
</author>
<published>2022-05-15T00:06:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=6a2efdda2f7075331cab36901a30d511468f60e7'/>
<id>urn:sha1:6a2efdda2f7075331cab36901a30d511468f60e7</id>
<content type='text'>
[REUSE] is a specification that aims at making file copyright
information consistent, so that it can be both human and machine
readable. It basically requires that all files have a header containing
copyright and licensing information. When this isn't possible, like
when dealing with binary assets, generated files or embedded third-party
dependencies, it is permitted to insert copyright information in the
`.reuse/dep5` file.

Oh, and it also requires that all the licenses used in the project are
present in the `LICENSES` folder, that's why the diff is so huge.
This can be done automatically with `reuse download --all`.

The `reuse` tool also contains a handy subcommand that analyzes the
project and tells whether or not the project is (still) compliant,
`reuse lint`.

Following REUSE has a few advantages over the current approach:

- Copyright information is easy to access for users / downstream
- Files like `dist/license.md` do not need to exist anymore, as
  `.reuse/dep5` is used instead
- `reuse lint` makes it easy to ensure that copyright information of
  files like binary assets / images is always accurate and up to date

To add copyright information of files that didn't have it I looked up
who committed what and when, for each file. As yuzu contributors do not
have to sign a CLA or similar I couldn't assume that copyright ownership
was of the "yuzu Emulator Project", so I used the name and/or email of
the commit author instead.

[REUSE]: https://reuse.software

Follow-up to b2eb10382941bef0914f4a0a4685b9033440aa9f
</content>
</entry>
<entry>
<title>common: Eliminate variable shadowing</title>
<updated>2022-06-13T22:19:22+00:00</updated>
<author>
<name>Morph</name>
<email>39850852+Morph1984@users.noreply.github.com</email>
</author>
<published>2022-05-27T00:33:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=716cced39900d225aedaf9520eca002b25b8dd6f'/>
<id>urn:sha1:716cced39900d225aedaf9520eca002b25b8dd6f</id>
<content type='text'>
GCC/Clang treats variables within lambdas as potentially shadowing those outside the lambda, despite them not being captured inside the lambda's capture list.
</content>
</entry>
<entry>
<title>common/detached_tasks: Wait for tasks before shutting down</title>
<updated>2021-06-22T07:27:44+00:00</updated>
<author>
<name>Rodrigo Locatti</name>
<email>rodrigo.locatti@gmail.com</email>
</author>
<published>2021-06-22T07:27:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=ee29cddce273da78849305e26ab69f8dc1491144'/>
<id>urn:sha1:ee29cddce273da78849305e26ab69f8dc1491144</id>
<content type='text'>
If this is not waited on, the synchronization primitives are destroyed
whe main exits and the detached task ends up signalling garbage and not
properly finishing.
</content>
</entry>
<entry>
<title>General: Tidy up clang-format warnings part 2</title>
<updated>2020-08-13T18:19:08+00:00</updated>
<author>
<name>Lioncash</name>
<email>mathew1800@gmail.com</email>
</author>
<published>2020-08-11T15:08:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=78ddcbe3ba0f8f5740149bff2054e2dffc0e9d83'/>
<id>urn:sha1:78ddcbe3ba0f8f5740149bff2054e2dffc0e9d83</id>
<content type='text'>
</content>
</entry>
<entry>
<title>general: Use deducation guides for std::lock_guard and std::unique_lock</title>
<updated>2019-04-01T16:53:47+00:00</updated>
<author>
<name>Lioncash</name>
<email>mathew1800@gmail.com</email>
</author>
<published>2019-04-01T16:29:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=eb88e9d08851f1aeb4716d43f220a06880bf42eb'/>
<id>urn:sha1:eb88e9d08851f1aeb4716d43f220a06880bf42eb</id>
<content type='text'>
Since C++17, the introduction of deduction guides for locking facilities
means that we no longer need to hardcode the mutex type into the locks
themselves, making it easier to switch mutex types, should it ever be
necessary in the future.
</content>
</entry>
<entry>
<title>Port web_service from Citra</title>
<updated>2018-10-02T13:30:48+00:00</updated>
<author>
<name>fearlessTobi</name>
<email>thm.frey@gmail.com</email>
</author>
<published>2018-09-16T18:05:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=92e939952cd87ae5d1bde5ec9ea5e95795876001'/>
<id>urn:sha1:92e939952cd87ae5d1bde5ec9ea5e95795876001</id>
<content type='text'>
</content>
</entry>
</feed>
