aparoksha/adwaita-swift
3
7
Fork 5
Code Issues 20 Pull Requests Actions Releases 1 Activity

[Question] Memory management #67

New Issue
Closed
opened 2025-08-12 16:38:35 +02:00 by Sylphrena · 2 comments
Sylphrena commented 2025-08-12 16:38:35 +02:00
Contributor
Copy Link

Hi! Thank you for this library!

This isn't really an issue, but a question out of curiosity, since I just recently picked up Swift and the source code is not entirely clear to me yet.

How is memory handled in adwaita-swift? Generally, in other languages, signals and property bindings prevent an object from being freed, leading to memory leaks unless disconnected properly.

Is there some closure data manager or ref toggling?

Thanks in advance!

Hi! Thank you for this library! This isn't really an issue, but a question out of curiosity, since I just recently picked up Swift and the source code is not entirely clear to me yet. How is memory handled in `adwaita-swift`? Generally, in other languages, signals and property bindings prevent an object from being freed, leading to memory leaks unless disconnected properly. Is there some closure data manager or ref toggling? Thanks in advance!
itjustcrashed commented 2025-08-15 07:30:04 +02:00
Copy Link

https://docs.swift.org/swift-book/documentation/the-swift-programming-language/automaticreferencecounting/

TL;DR Swift figures out when to free memory and how long something should live. Additionally, when a view is destroyed its state is destroyed (and freed) too. You don’t have to worry about memory management all that much, and Swift 6 literally won’t let you create a memory leak. If you see a leak in your app, it is coming from Libadwaita, which is written in C.

https://docs.swift.org/swift-book/documentation/the-swift-programming-language/automaticreferencecounting/ TL;DR Swift figures out when to free memory and how long something should live. Additionally, when a view is destroyed its state is destroyed (and freed) too. You don’t have to worry about memory management all that much, and Swift 6 literally won’t let you create a memory leak. If you see a leak in your app, it is coming from Libadwaita, which is written in C.
👍 2
Sylphrena commented 2025-08-15 19:23:13 +02:00
Author
Contributor
Copy Link

Thank you!

Thank you!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: aparoksha/adwaita-swift#67
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?