Mirror of the Rel4tion website/wiki source, view at <http://rel4tion.org>

[[ 🗃 ^yEzqv rel4tion-wiki ]] :: [📥 Inbox] [📤 Outbox] [🐤 Followers] [🤝 Collaborators] [🛠 Commits]

Clone

HTTPS: git clone https://vervis.peers.community/repos/yEzqv

SSH: git clone USERNAME@vervis.peers.community:yEzqv

Branches

Tags

master :: projects / tosaf / tickets /

2.mdwn

[[!tag /tickets/class/idea]]

[[!meta title=“Real-time library path changes”]]

Consider supporting library path changes in real-time, after the program started running and doing things. But then consider using mutexes to support safe multi-threaded write access to the library path.

Is this thing ever useful? Is there a reason for the library path to change in real-time? If there aren’t specific use cases, avoid cluttering the source code (or use a separate feature branch) until use cases appear.

[See repo JSON]