![]() I'm still open to design change suggestions, bugs, feature requests, or anything else that might be worth doing before 1.0. I've been able to reliably use this for IPC on cross-platform apps (namely to dump error output into another terminal for debugging a cross-platform TUI app). Update in case anyone runs into this thread again: Many API improvements have been made and bugs have been squashed in the last 10 days since I made this post. I basically want to get to a point where the behavior API is entirely reliable cross-platform before 1.0. In its current state, I'm sure there are some bugs and bits of functionality that don't quite match up between Windows and Unix systems. The point of this post here is to get some exposure, ideas, and also just see if this is something other developers might find useful. I also created a binary crate alongside it: pipe_watcher, that makes it easy to pipe output from a Rust program into another terminal or the stdin of another program. The idea is to have a simple API that makes it as simple as possible to direct I/O in useful ways using named pipes. For a long time I've wanted a simple abstraction layer that can get you the best of both worlds in a cross-platform way. Basically, named-pipes in Unix are really easy and useful, but Windows named pipes are a bit tricky and painful. This isn't a huge project, but it's a bit of useful functionality I've wanted for a while so I thought I'd share a bit about it. We'll do our best to keep these links up to date, but if we fall behind please don't hesitate to shoot us a modmail. This is not an official Rust forum, and cannot fulfill feature requests. Err on the side of giving others the benefit of the doubt.Īvoid re-treading topics that have been long-settled or utterly exhausted. Please create a read-only mirror and link that instead.Ī programming language is rarely worth getting worked up over.īe charitable in intent. If criticizing a project on GitHub, you may not link directly to the project's issue tracker. Post titles should include useful context.įor Rust questions, use the stickied Q&A thread.Īrts-and-crafts posts are permitted on weekends.Ĭriticism is encouraged, though it must be constructive, useful and actionable. For content that does not, use a text post to explain its relevance. Posts must reference Rust or relate to things using Rust. We observe the Rust Project Code of Conduct. Strive to treat others with respect, patience, kindness, and empathy. Facepunch has not confirmed anything either way, leading gamers to speculate about the much. Although plenty of console gamers are excited about Facepunch Studio's upcoming port, many gamers are worried about whether or not it will support cross-platform play. Please read The Rust Community Code of Conduct The Rust Programming LanguageĪ place for all things related to the Rust programming language-an open-source systems language that emphasizes performance, reliability, and productivity. The epic survival game Rust is finally making the jump to PlayStation 4 and Xbox One. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |