Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9149927
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 17, 20262026-06-17T11:32:39+00:00 2026-06-17T11:32:39+00:00

[self.foo setBlock:^{ [self doSomething]; // causes warning }]; versus [self.foo setBlock:^{ self.bar = baz;

  • 0
[self.foo setBlock:^{
    [self doSomething]; // causes warning
}];

versus

[self.foo setBlock:^{
    self.bar = baz;     // does not cause warning
}];

The warning being “Capturing self strongly in this block is likely to lead to a retain cycle.”

Don’t both lead to a strong reference?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-17T11:32:39+00:00Added an answer on June 17, 2026 at 11:32 am

    This is a compiler bug and you should file a bug report with Apple.

    Both are the same, a.b = c is just a different way for writing [a setB: c]. If the compiler handles one differently from the other this is a bug.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Initialising the Foo object does run the method func(), but the value of self.a
I have the following structure: class foo(object): class bar(object): def __init__(self, parent): self._parent=parent #this
Suppose I have: class myclass: def __init__(self): self.foo = bar where the value of
class ClassName(object): def __init__(self, foo, bar): self.foo = foo # read-write property self.bar =
Given the following property definition: @property (nonatomic,retain) MyObject* foo; does the following code cause
Suppose I have this class: class MyClass(object): def uiFunc(self, MainWindow): self.attr1 = foo self.attr2
I'm new to Python. I have a method that begins: def foo(self, list): length
I will go straight to the example: class Foo: @execonce def initialize(self): print 'Called'
I used core data to do this: NSManagedObjectContext *m = [self managedObjectContext]; Foo *f
I'm pretty new at python and I was wondering if this: def func(self, foo):

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.