• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
  • entries
    625
  • comments
    1446
  • views
    1006490

Type inference and anonymous returns

Sign in to follow this  
Followers 0
ApochPiQ

233 views

It's been a productive holiday for Epoch!

In addition to adding generalized support for anonymous temporary constructors as well as overloaded constructors, I've added some nice convenience features. Specifically, it is now possible to return anonymous expressions directly from functions, thanks to some hefty upgrades to the type inference capabilities of the compiler.


For example, it used to be necessary to write code like this:

increment : (integer(value)) -> (integer(ret, value + 1))

Even worse, in previous versions of Epoch, it wasn't possible to directly compute expressions in the return value initializer, so you had the more cumbersome version:

increment : (integer(value)) -> (integer(ret, 0)) { ret = value + 1 }


This is all superfluous now. Although function parameters typically still require type annotations, much of the rest of the syntax can be elided entirely. This permits nice, compact definitions for trivial functions:

increment : (integer(value)) -> (value + 1)


Again, type inference plays heavily into this, and it is now necessary to run the compiler across the code several times to complete all inference passes. This leads to a minor increase in build times but at the benefit of much cleaner code. I may find a more intelligent way to do inference later as well, which might reduce the need for extra inference passes, or better, localize the passes so the compiler doesn't spend time recompiling code that doesn't need any more work done on it.


Pattern matching on function parameters makes this even more powerful. For instance, I can write a program like the following:

returnstring : (string(param)) -> (param)
returninteger : (integer(param)) -> (param * 2)

fib : (0) -> (1)
fib : (1) -> (1)
fib : (integer(n)) -> (integer(ret, fib(n - 1) + fib(n - 2)))

entrypoint : () -> ()
{
debugwritestring(returnstring("test"))
debugwritestring(cast(string, returninteger(21)))
debugwritestring(cast(string, fib(5)))
}


Note that I still have to explicitly provide a return value for the general-case overload of fib. This is because, in Epoch, overloads can differ by only their return types; so the type inference engine can't tell if fib returns an integer or a real or what have you.

I may be able to improve this in the future by adding a simple heuristic: if no overloads differ by return type, a recursive pattern-matched function can be inferred to return the same type as all the other overloads. This would eliminate the need to specify a return variable for the general case of fib above, making things even more compact:

fib : (integer(n)) -> (fib(n - 1) + fib(n - 2))


There are a few cases where inference will fail entirely and get stuck in an infinite loop; I need to add some safety checks to make sure the inference doesn't try to run more than a sane number of passes over the code, or at least halts if it stops making forward progress.


I have only a handful of items left to do for Release 11, and then I'll be considering when to kick it out the door. Stay tuned - this will be a big one!

0
Sign in to follow this  
Followers 0


0 Comments


There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now