Zoxc

> ::hi()
mirb:
    Parsing Error: Can only reference constants when leaving out the lookup expression (Use ::Object to access non-constants)
    Input[1]: ::hi()
              ~~~~~~
mri:
    SyntaxError: (irb):6: syntax error, unexpected tIDENTIFIER, expecting tCONSTANT
    ::hi()
        ^

Zoxc

- Reads from client buffers in weston must be converted to linear gamma. Client buffers can be presented to weston with sRGB or linear gamma.
	The server-side wl_drm will use sRGB formats to convert it for weston if that's available.
	Should the existing SHM/DRM formats be declared as having sRGB gamma? If so, should the premultiplied color format be linear_to_srgb(color * alpha) (the format OpenGL and pixman uses for sRGB)?
	How should you pass on whether or not the compositor prefers linear gamma to wayland_drm_init in mesa? (This is needed to disable gamma correction for performance reasons)
		Options:
			- Replace the eglQueryWaylandBufferWL, eglCreateImageKHR sequence with:
			  EGLBoolean eglSetupWaylandBufferWL(EGLDisplay dpy, struct wl_buffer *buffer, const EGLint *attrib_list, EGLint *format, EGLint *planes, EGLImageKHR *images);
			- Call an eglSetupWaylandBufferWL function before doing anything with a wl_buffer (but keep the eglQueryWaylandBufferWL, eglCreateImageKHR sequence)
			- Add eglDisplayAt

Zoxc

# class is Scala or Haskell like traits or type classes

class Constructor[*Args] # Args is variadic
{
	type Constructed
	static construct(obj: *Constructed, args: Args): unit
}

class Destructable # All types have instance of this
{

Zoxc

#include <stdio.h>
#include <math.h>
#include <swl.h>

#include "gles.hpp"
#include <ft2build.h>
#include FT_FREETYPE_H

FT_Library library;

Zoxc

Trivial:
	Type trailing with colon
		global, other_global: int
		yet_another_global: () -> string
		
		func()
			a, c: int
			b := 4

	Type trailing and var keyword

Zoxc

mutex commit

atomic<int> render_complete_count
signal resizing_complete

apply_pending_state(surface) {
	wl_surface_attach(surface, ...)
	wl_surface_damage(surface, ...)
}

Zoxc

use "../core"

enum Token
	None
	Unknown
	Id

struct Lexer
	struct State
		lexer *Lexer

Zoxc

Capability system

This is a sketch of a capability system which utilised data and operations in kernel mode.

There are 2 kernel objects used to support the capability system, Vat and Call. Cap is a global identifier of a capability consisting of a Vat reference and a vat defined number.

Messages

enum Message {

Zoxc

Remote procedure calls in Avery

Introduction

Avery's RPCs are based on capabilities. A capability is a reference to an object which the process has previously received. If you do not have a capability to an object, you cannot communicate with it.

You can do asynchronous calls to objects. These in calls, arguments and return values can contain both bytes and capabilities. If you send a capability to another process it gains access to it.

Objects belong to an event loop (a kernel object) and all messages sent to it is queued there.

Zoxc

// A function pointer and some data to pass to the callback
pub struct Callback<R> {
	pointer: fn (R, *const ()),
	data: *const (),
}

// This is the trait implemented for generators
pub trait Future {
 	type Return;