Ophestra 0e2fb1788f internal/pipewire: implement Registry::Destroy ...

This requires error handling infrastructure in Core that does not yet exist, so it is not exported for now. It has been manually tested via linkname against PipeWire.

Signed-off-by: Ophestra <cat@gensokyo.uk>

2025-12-10 01:25:30 +09:00

..

testdata

internal/pipewire: store sample iovec continuously

2025-11-28 00:35:10 +09:00

client_test.go

internal/pipewire: seq access method for consume

2025-12-07 17:07:30 +09:00

client.go

internal/pipewire: specify opcode and file count with message

2025-12-07 13:54:11 +09:00

core_test.go

internal/pipewire: implement Registry::Destroy

2025-12-10 01:25:30 +09:00

core.go

internal/pipewire: implement Registry::Destroy

2025-12-10 01:25:30 +09:00

header_test.go

internal/pipewire: implement Core::Error

2025-11-30 01:39:39 +09:00

header.go

internal/pipewire: implement client context

2025-12-02 06:03:21 +09:00

pipewire_test.go

internal/pipewire: implement Registry::GlobalRemove

2025-12-10 01:00:03 +09:00

pipewire.go

internal/pipewire: expose connection props

2025-12-09 06:51:12 +09:00

pod_test.go

internal/pipewire: improve protocol error messages

2025-12-04 03:15:58 +09:00

pod.go

internal/pipewire: specify opcode and file count with message

2025-12-07 13:54:11 +09:00

securitycontext_test.go

internal/pipewire: constants from pipewire/keys.h

2025-12-05 03:27:30 +09:00

securitycontext.go

internal/pipewire: set finalizer on scc

2025-12-07 17:29:22 +09:00

spa_test.go

internal/pipewire: use type name in error strings

2025-12-04 02:29:27 +09:00

spa.go

internal/pipewire: constants from pipewire/keys.h

2025-12-05 03:27:30 +09:00