Give parent to an instance before giving it properties?

[Zadkay]

Hello developers, I have a question, really what is the correct way to create an instance, my question is this, Suppose I have to create an instance, an example is a part, but first I give it its properties and then the parent, Example:

local Part = Instance.new("Part")
Part.Anchored = true
--And another properties...--
Part.Parent = workspace

and another example would be to create the part and give it a parent first, Example:

local Part = Instance.new("Part")
Part.Parent = workspace
Part.Anchored = true
--And another properties...--

• Is there a change in these two?
• Which of these two ways do you use?

Answer here below!

[lluckvy (aaron)]

Parent it first, because it wouldn’t make sense to Anchor something that has no place. I use the second one

But technically speaking, they’re both correct.

[PorgDotOrg (Porg)]

They are the same thing. I use the first one more, just because I think it’s cleaner. Also, I suggest putting this post in #help-and-feedback:scripting-support

[kingerman88]

I’m not sure if this is still relevant today, however I believe that there is a performance negative for setting the parent first then the properties. (This could just be for the instance.new() parent property though)

PSA: Don't use Instance.new() with parent argument

I’ve discovered a pretty bad performance issue in one of top games that has to do with Instance.new and wanted to write about this, since this is not obvious unless you know the system inside out. Tthere are several ways to create a ROBLOX object in Lua: local obj = Instance.new(‘type’); fill obj fields local obj = Instance.new(‘type’, parent); fill obj fields local obj = util.Create(‘type’, { field1 = value1, … }) If you care at all about performance, please only use the first option - I wi…

[Zadkay]

It still has some logic now that I see, but anyway I think it works the same in both ways, Thanks for your comment!