mirror of
				https://github.com/bspeice/speice.io
				synced 2025-11-03 18:10:32 -05:00 
			
		
		
		
	Remove extraneous links
This commit is contained in:
		@ -238,9 +238,3 @@ fn main() {
 | 
			
		||||
 | 
			
		||||
And with that, we've now got a functioning project. Here's the content I'm planning to go over next as we build up
 | 
			
		||||
some practical examples of Cap'N Proto in action:
 | 
			
		||||
 | 
			
		||||
## Next steps
 | 
			
		||||
 | 
			
		||||
Part 2: Using [TypedReader](https://github.com/capnproto/capnproto-rust/blob/master/src/message.rs#L181) to send messages across thread boundaries
 | 
			
		||||
 | 
			
		||||
Part 3: Serialization and Deserialization of multiple Cap'N Proto messages
 | 
			
		||||
 | 
			
		||||
@ -100,7 +100,7 @@ preventing us from doing something that really should be legal?
 | 
			
		||||
This is what is known as [fighting the borrow checker](https://doc.rust-lang.org/1.8.0/book/references-and-borrowing.html).
 | 
			
		||||
Let our crusade begin.
 | 
			
		||||
 | 
			
		||||
## Attempt 2: Put the `Reader` in a `Box
 | 
			
		||||
## Attempt 2: Put the `Reader` in a `Box`
 | 
			
		||||
 | 
			
		||||
The [`Box`](https://doc.rust-lang.org/std/boxed/struct.Box.html) type allows us to convert a pointer we have
 | 
			
		||||
(in our case the `point_reader`) into an "owned" value, which should be easier to send across threads.
 | 
			
		||||
@ -241,7 +241,3 @@ And while we've left Rust to do the dirty work of actually moving the `point_rea
 | 
			
		||||
we could also use things like [`mpsc` channels](https://doc.rust-lang.org/std/sync/mpsc/index.html) to achieve a similar effect.
 | 
			
		||||
 | 
			
		||||
So now we're able to define basic Cap'N Proto messages, and send them all around our programs.
 | 
			
		||||
 | 
			
		||||
## Next steps:
 | 
			
		||||
 | 
			
		||||
[Part 1: Setting up a basic Cap'N Proto Rust project](http://bspeice.github.io/captains-cookbook-part-1.html)
 | 
			
		||||
 | 
			
		||||
		Reference in New Issue
	
	Block a user