Function.InvokeAfter() RRS feed


  • The use case for Function.InvokeAfter is to invoke a function after a certain delay. I believe Curt will be able to give you more information as to why the signatures diverge exactly, but the current signature doesn't prevent you from using is in any way. You would simply invoke the function with parameters in a lambda passed to Function.InvokeAfter.
    Monday, April 27, 2015 9:18 PM
  • It's just separation of concerns. Despite similar names, these functions don't have anything to do with each other.

    The primary use case for Function.Invoke is when you don't know the exact number of parameters in advance -- because otherwise, you could just invoke the function directly. I don't think I've ever run into a need for it.

    Monday, April 27, 2015 10:49 PM

All replies