Typesafe Promise implementation for Roblox Luau
Find a file
2019-09-12 03:59:02 -04:00
.vuepress Make cancellation propagate downstream 2019-09-12 03:58:56 -04:00
lib Create usage guide 2019-09-12 03:59:02 -04:00
modules Start implementing tests, add lemur and testez dependencies 2018-01-31 15:29:04 -08:00
.editorconfig Initial dump 2018-01-25 17:21:58 -08:00
.gitignore Update for release 2019-09-10 15:34:06 -04:00
.gitmodules Start implementing tests, add lemur and testez dependencies 2018-01-31 15:29:04 -08:00
.luacheckrc Start implementing tests, add lemur and testez dependencies 2018-01-31 15:29:04 -08:00
.luacov Add .gitignore and .luacov 2018-02-01 11:21:41 -08:00
CHANGELOG.md Make cancellation propagate downstream 2019-09-12 03:58:56 -04:00
default.project.json Update for release 2019-09-10 15:34:06 -04:00
LICENSE Update LICENSE 2019-09-10 00:29:21 -04:00
package-lock.json Make cancellation propagate downstream 2019-09-12 03:58:56 -04:00
package.json Make cancellation propagate downstream 2019-09-12 03:58:56 -04:00
README.md Update README.md 2019-09-10 17:14:24 -04:00
spec.lua Start implementing tests, add lemur and testez dependencies 2018-01-31 15:29:04 -08:00

Roblox Lua Promise

An implementation of Promise similar to Promise/A+.

View docs

Motivation

The way Roblox models asynchronous operations by default is by yielding (stopping) the thread and then resuming it when the future value is available. This model is not ideal because:

  • Functions you call can yield without warning, or only yield sometimes, leading to unpredictable and surprising results. Accidentally yielding the thread is the source of a large class of bugs and race conditions that Roblox developers run into.
  • It is difficult to deal with running multiple asynchronous operations concurrently and then retrieve all of their values at the end without extraneous machinery.
  • When an asynchronous operation fails or an error is encountered, Lua functions usually either raise an error or return a success value followed by the actual value. Both of these methods lead to repeating the same tired patterns many times over for checking if the operation was successful.
  • Yielding lacks easy access to introspection and the ability to cancel an operation if the value is no longer needed.

Goals

This Promise implementation attempts to satisfy these traits:

  • An object that represents a unit of asynchronous work
  • Composability
  • Predictable timing

Example

This Promise implementation finished synchronously. In order to wrap an existing async API, you should use Promise.spawn in order to prevent your calling thread from accidentally yielding.

local HttpService = game:GetService("HttpService")

-- A light wrapper around HttpService
-- Ideally, you do this once per project per async method that you use.
local function httpGet(url)
	return Promise.async(function(resolve, reject)
		local ok, result = pcall(HttpService.GetAsync, HttpService, url)

		if ok then
			resolve(result)
		else
			reject(result)
		end
	end)
end

-- Usage
httpGet("https://google.com")
	:andThen(function(body)
		print("Here's the Google homepage:", body)
	end)
	:catch(function(err)
		warn("We failed to get the Google homepage!", err)
	end)