{"push_id":2224100951,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"d7dec201c64a3cb30f9741091098db78ab5b132f","before":"897a70a61f3989a732cc5d68058401508b401d4c","commits":[{"sha":"d7dec201c64a3cb30f9741091098db78ab5b132f","author":{"name":"Eric Mellino","email":"3b183e62f917c179f3d5ce45440b743c74c61109@gmail.com"},"message":"Fully implement all Texture-related functions for all Texture types.\n\n* This change fills in all of the Texture-related functionality for\n  all backends, and makes a few breaking API changes in order to\n  better separate the different kinds of Texture objects available.\n* There is a new enumeration, \"TextureType\", which simply identifies\n  whether a Texture is a 1D, 2D, or 3D Texture.\n* TextureDescription now has a TextureType field, which must be\n  specified in order to control the type of Texture created.\n  Previously, Textures were always being implicitly created as 2D\n  Textures. Now, the type must be explicitly specified upon creation.\n* There are three utility functions on TextureDescription, which\n  can be used to succinctly describe a 1D, 2D, or 3D Texture.\n  * Texture1D(), Texture2D(), and Texture3D().\n* A large number of functional tests have been added to validate\n  the new code paths.","distinct":true,"url":"https://api.github.com/repos/mellinoe/veldrid/commits/d7dec201c64a3cb30f9741091098db78ab5b132f"}]}
{"actor":{"display_login":"mellinoe"}}