---

yaml
---
r: 148455
b: refs/heads/try2
c: 67d83ac
h: refs/heads/master
i:
  148453: 56e24fd
  148451: 56a115c
  148447: b4d38c1
v: v3

Author: Matthias247

[refs]

@@ -5,7 +5,7 @@ refs/heads/snap-stage3: 78a7676898d9f80ab540c6df5d4c9ce35bb50463
 refs/heads/try: 519addf6277dbafccbb4159db4b710c37eaa2ec5
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
-refs/heads/try2: 188167c4b3ab42f1d0dc793365819afe28719df5
+refs/heads/try2: 67d83ac40af2c2e20c44e4c16b53e500880a7439
 refs/heads/dist-snap: ba4081a5a8573875fed17545846f6f6902c8ba8d
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503

branches/try2/doc/guide-ffi.md

@@ -329,6 +329,12 @@ channel where the writing end (`Chan`) is used exclusively from the C callback
 to queue events. The reading end (`Port`) is used in the Rust task which owns
 the wrapper object.
 
+Depending on the type of data in the event you might want to convert callback
+data from C into a more suitable Rust structure before sending it into the
+channel. E.g. it makes sense to convert C strings (`char*`) into Rust strings.
+You could also use Rust enumerations to differentiate between multiple types
+of events and their data.
+
 Putting this together a wrapper for a library that uses a background thread
 that sends events could look like: