Redstone Integrator Pull Event

[Erabior]

Describe your idea

Redstone pull event for redstone integrators. I feel it makes sense as the computers have os.pullEvent("redstone")
I.E.
local redR=peripheral.wrap('right')
inputlevel=redR.pullEvent("redstone")

Describe alternatives you've considered if you've any

alternatively, perhaps make the integrators simply output a redstone signal on the side facing the computer? This would make os.pullEvent("redstone") function and it would be up to the user to determine which integrator and what side. This would still save a bit of work and does not seem to difficult to implement.

Additional context

No response

Linked Issues

No response

[djmattyg007]

perhaps make the integrators simply output a redstone signal on the side facing the computer

IMO this isn't particularly practical, as it assumes the Rs bridge is placed directly next to the computer in the world, rather than connected via wired modems.

I like the suggestion in general though 👍

[Peekofwar]

I would also like some way to "interrupt" the program whenever something is detected by a redstone integrator rather than having to constantly scan a ton of redstone integrators for active signals.

Something like os.pullEvent("redstoneIntegrator").
Could return:
1 event name
2 side string
3: peripheral name
Example - What it would look like if you depressed a button on the north side of an integrator:

lua> while true do require("cc.pretty").pretty_print({os.pullEvent("redstoneIntegrator")}) end
{
  "redstoneIntegrator",
  "north",
  "redstoneIntegrator_5",
}
{
  "redstoneIntegrator",
  "north",
  "redstoneIntegrator_5",
}

The reason I'd rather have it done this way as apposed the the method proposed by the original author of this ticket, is because it would make it simpler to track a large number of integrators as they'd all send their event to the global event queue.

[Tcheikovski]

IMO the solution @Peekofwar suggests is more appropriate as pulling the event from the computer seems more maintainable and more consistent with the other peripheral events (ex: monitor_resize, disk_eject, etc...)
Also I think this feature should have an higher priority as the redstone event is about 50% of the usage of redstone api in many programs, making the RedstoneIntegrator pretty much useless until the events are implemented :/