Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Image could be malloc'd instead of GC allocated #14

Closed
p0nce opened this issue Apr 22, 2015 · 1 comment
Closed

Image could be malloc'd instead of GC allocated #14

p0nce opened this issue Apr 22, 2015 · 1 comment

Comments

@p0nce
Copy link

p0nce commented Apr 22, 2015

I'm a bit wary of GC scan time for large ae.utils.graphics.image.Image.
Since image data is not supposed to be pointers, perhaps we could instead use malloc/free?
https://github.com/CyberShadow/ae/blob/master/utils/graphics/image.d#L75
@p0nce p0nce changed the title Image could malloc'd instead of GC allocated Image could be malloc'd instead of GC allocated Apr 22, 2015
@CyberShadow
Copy link
Owner

The GC already does not scan memory areas which do not contain pointers.

@p0nce p0nce closed this as completed Apr 22, 2015
@p0nce p0nce mentioned this issue Apr 27, 2015
Closed
FeepingCreature pushed a commit to FeepingCreature/ae that referenced this issue Jan 12, 2018
@belka-ew
Merge pull request CyberShadow#14 from funkwerk/unittest-attributes
dfbb771 
Unittest attributes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@CyberShadow @p0nce