The book should use the inclusion syntax for its examples

[torkleyy]

We can use

{{#include file.rs:2:10}}

to include the code from our examples in the book, so we don't need to duplicate everything.

[torkleyy]

http://rust-lang-nursery.github.io/mdBook/format/mdbook.html#including-files

[torkleyy]

http://rust-lang-nursery.github.io/mdBook/format/mdbook.html#including-files

[Rhuagh]

Ah, cool. Sounds excellent, then we get testing on it aswell.

[Rhuagh]

Ah, cool. Sounds excellent, then we get testing on it aswell.

[Xaeroxe]

I'm not sure including arbitrary line numbers is a good idea. It's really easy to have these offset by simple PR changes such as formatting or otherwise. It could become so difficult to maintain correctly that duplication might be preferable.

[Xaeroxe]

I'm not sure including arbitrary line numbers is a good idea. It's really easy to have these offset by simple PR changes such as formatting or otherwise. It could become so difficult to maintain correctly that duplication might be preferable.

[torkleyy]

@Xaeroxe Yeah, I realized that, too.

[torkleyy]

@Xaeroxe Yeah, I realized that, too.

[Xaeroxe]

So, after having realized that do you still feel this is a good solution?

[Xaeroxe]

So, after having realized that do you still feel this is a good solution?

[torkleyy]

At least for the complete examples where we don't need lines, this does makes sense.

[torkleyy]

At least for the complete examples where we don't need lines, this does makes sense.

[torkleyy]

Like I think every pong chapter has them at the end, so we can do it for those.

[torkleyy]

Like I think every pong chapter has them at the end, so we can do it for those.

[Moxinilian]

I'm not sure this is a good idea either. The representation in the repo always contains additional details to make it work in the context of the repo, most notably the assets path. Those details don't belong in the book.

[Moxinilian]

I'm not sure this is a good idea either. The representation in the repo always contains additional details to make it work in the context of the repo, most notably the assets path. Those details don't belong in the book.