# Byte-sized Swift: Building Tiny Games for the Playdate

**URL:** <https://forums.swift.org/t/byte-sized-swift-building-tiny-games-for-the-playdate/70615>\
**Category:** Community Showcase\
**Tags:** swiftorg-blog, embedded\
**Created:** [March 12, 2024, 5:06pm UTC](https://forums.swift.org/t/byte-sized-swift-building-tiny-games-for-the-playdate/70615 "2024-03-12T17:06:29Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![rauhul](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/rauhul/32/35207_2.png) [@rauhul](https://forums.swift.org/u/rauhul)\
**Post date:** [March 13, 2024, 2:55am UTC](https://forums.swift.org/t/byte-sized-swift-building-tiny-games-for-the-playdate/70615/8 "2024-03-13T02:55:07Z")

</div>

> [@wadetregaskis](#):
>
> ### Random numbers

As noted by Ben and Steve, this is a _current_ limitation of embedded swift, but won't be forever!

> [@wadetregaskis](#):
>
> ### Why `UnsafeMutablePointer`?

I think I could use a buffer pointer here, but as noted later in the post the cost of redundant null checks actually adds up on this platform and similarly the bounds checks might have an appreciable effect on Conways performance.

> [@wadetregaskis](#):
>
> ### Bit vectors and matrices

I didn't consider using other packages because I was building with makefiles. I also am not sure if that package uses features not available in embedded mode.

> [@wadetregaskis](#):
>
> ### Unsafe\*Ptr ergonomics / C bridging challenges

I actually tried to make this, but couldn't get it to work with function pointers! Have you had success with dynamic member look up and closures/function pointers?

---

_[View the full topic](https://forums.swift.org/t/byte-sized-swift-building-tiny-games-for-the-playdate/70615)._
